AI agents use resolve-allowance to create or update resources in MCPilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPilot environment.
An AI agent can call resolve-allowance faster than any human can review — one bad instruction and it creates or modifies resources in MCPilot by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Resolve the result of allowance. It is categorised as a Write tool in the MCPilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPilot MCP server in PolicyLayer and add a rule for resolve-allowance: 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 MCPilot. Nothing to install.
resolve-allowance 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 resolve-allowance 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 resolve-allowance. 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.
resolve-allowance is provided by the MCPilot MCP server (xiawpohr/mcpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.