AI agents use set_session_ready to create or update resources in Repl — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Repl environment.
An AI agent can call set_session_ready faster than any human can review — one bad instruction and it creates or modifies resources in Repl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Mark a session as ready by specifying the detected prompt pattern. Supports regex patterns (e.g.,. It is categorised as a Write tool in the Repl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Repl MCP server in PolicyLayer and add a rule for set_session_ready: 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 Repl. Nothing to install.
set_session_ready 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 set_session_ready 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 set_session_ready. 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.
set_session_ready is provided by the Repl MCP server (takafu/repl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.