Provides security guidance about Recall operations without exposing sensitive information
AI agents call security_guidance to retrieve information from Recall MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents security guidance information. It is explicitly stated to not expose sensitive information and does not create, modify, delete, or execute operations. It is a simple informational/advisory read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Provides security guidance about Recall operations without exposing sensitive information'—a purely informational operation with no data modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access security_guidance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Recall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for security_guidance:
{
"version": "1",
"default": "deny",
"tools": {
"security_guidance": {}
}
}security_guidance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Provides security guidance about Recall operations without exposing sensitive information. It is categorised as a Read tool in the Recall MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Recall MCP Server MCP server in PolicyLayer and add a rule for security_guidance: 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 Recall MCP Server. Nothing to install.
security_guidance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the security_guidance 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 security_guidance. 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.
security_guidance is provided by the Recall MCP Server MCP server (recallnet/recall-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Recall MCP Server, 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.
9 Recall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.