Hey,
thanks for all the answers. Great community!
I couldn’t reply since there was is a post limit of 3 for the first day and I wasn’t around at the weekend.
Anyway, btt:
@rAWTAZ: The behavior is getting a parameter for the path in which a file should be saved and most of the time the path consists of some variation of the model’s attributes.
@zilles: Thank you for your two ideas. I think I will go with your 2nd one which almost perfectly fits my scenario.
Thank you and everyone else for helping!
Edit 1: I just found out that you can’t pass functions in PHP. Too bad, nice idea though :-/
I think I will try your first idea now, if noone else nor me comes up with a better idea.
Edit 2: It’s not really generic if I require every model that uses the behavior to implement the functions needed for the parameters. It sure is more generic then the other ideas but if someone else has a new idea about this, I would be glad to read it!
Edit 3: Okay, it gets worse:
With the functions implemented in the model I var_dumped the return values in the behavior. And what did I get? Empty values. So the same output I got when I just passed that model’s attributes. 
Edit 4 (Hopefully the last):
It works when I not just return the attributes but connect them to an empty string:
return $model->id . '';
For now I will try to work with this version!
Edit 5 (Nope!):
This worked for the filename thing, but I just felt what losing generecity feels like… There is one ex-parameter, now function, in one of the models which needs to have different parameters at different times(the behavior is called twice in that model). So this solution would only work out with way too many dirty little fixes.
I’m still searching for that perfect one 