mcp 0.5.0 - can agent modify tool schemas at runtime
tested this yesterday with a filesystem tool.... added the schema in tool registration with strict types and constraints but wondering if the agent can modify or override the schema during execution specifically: can agent change param types, remove required fields, or add new params that weren't in original schema? need to know for security model
Yeah we ran into this exact scenario in staging last week testing mcp 0.5.0 with a stripe tool!! Agent can't modify tool schemas at runtime - schema gets locked when the tool registers with the mcp server. We tried to dynamically adjust rate limiting params based on api response headers (you know, the way every real api client works) but schema is completely immutable after registration. Does the schema at least support optional params that can be conditionally required, or is everything locked at registration time?
tested this on mcp 0.5.0-patch2 yesterday with a postgres tool. agent can't modify schemas at runtime - schema is locked when tool registers. tried to dynamically add params based on query complexity and it just ignored the new fields