Get all mandatory and forbidden rules (direct SQL, cached).
AI agents call memory_get_rules to retrieve information from Claude Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns existing rule data without creating, modifying, deleting, or executing external operations. The mention of 'direct SQL' and 'cached' indicates efficient read-only access to stored rules. Even though it accesses rule definitions, fetching them poses minimal risk unless the rules themselves contain sensitive secrets, but the tool itself performs only retrieval.
From the tool's definition Tool name contains 'get' and description states 'Get all mandatory and forbidden rules (direct SQL, cached)' — this is a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get all mandatory and forbidden rules (direct SQL, cached). It is categorised as a Read tool in the Claude Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory MCP server in PolicyLayer and add a rule for memory_get_rules: 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 Claude Memory MCP. Nothing to install.
memory_get_rules 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 memory_get_rules 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 memory_get_rules. 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.
memory_get_rules is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →