User explicitly confirms they want to proceed to the next step
AI agents use confirm_and_proceed to create or update resources in MCP Project Initializer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Project Initializer environment.
An AI agent can call confirm_and_proceed faster than any human can review — one bad instruction and it creates or modifies resources in MCP Project Initializer by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
User explicitly confirms they want to proceed to the next step. It is categorised as a Write tool in the MCP Project Initializer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Project Initializer MCP server in PolicyLayer and add a rule for confirm_and_proceed: 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 MCP Project Initializer. Nothing to install.
confirm_and_proceed 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 confirm_and_proceed 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 confirm_and_proceed. 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.
confirm_and_proceed is provided by the MCP Project Initializer MCP server (syndicats/mcp-initializer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.