update_mission_params
AI agents use update_mission_params to create or update resources in resQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your resQ MCP Server environment.
The name implies writing/updating configuration or parameters for an active mission in an emergency response system. Given the critical nature of the resQ emergency response context (drone deployments, incident response), modifying mission parameters could have significant real-world consequences. However, the empty description lowers confidence — it could also be Execute-level if it triggers live mission changes.
From the tool's definition Tool name 'update_mission_params' suggests modifying mission parameters; description is empty and uninformative.
Attacks that exploit this kind of access
update_mission_params. It is categorised as a Write tool in the resQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the resQ MCP Server MCP server in PolicyLayer and add a rule for update_mission_params: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches resQ MCP Server. Nothing to install.
update_mission_params is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_mission_params rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for update_mission_params. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
update_mission_params is provided by the resQ MCP Server MCP server (resq-software/pypi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →