Rebuild session indexes from records after crash/corruption.
AI agents use proxy_session_recover to create or update resources in Proxy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxy environment.
This tool reconstructs/rebuilds session index data from existing records, which is a write/repair operation. It modifies internal state (indexes) but does not irreversibly delete data or execute external commands. The blast radius is medium — misuse could corrupt or incorrectly rebuild session state, affecting ongoing traffic capture or proxy sessions.
From the tool's definition Rebuild session indexes from records after crash/corruption
Documented attack patterns abuse exactly the kind of access proxy_session_recover gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for proxy_session_recover:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_session_recover": {
"limits": [
{
"counter": "proxy_session_recover_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} proxy_session_recover stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rebuild session indexes from records after crash/corruption. It is categorised as a Write tool in the Proxy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxy MCP server in PolicyLayer and add a rule for proxy_session_recover: 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 Proxy. Nothing to install.
proxy_session_recover 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 proxy_session_recover 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 proxy_session_recover. 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.
proxy_session_recover is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.