List scopes with pagination and hierarchy
AI agents call scope_list to retrieve information from MCP Associative Memory 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 lists existing scopes with pagination and hierarchical organization. No data is created, modified, deleted, or affected externally. The 'list' operation is a standard read action that queries and returns existing information, making it a Read category tool with low severity due to its non-destructive nature.
From the tool's definition Tool name 'scope_list' and description 'List scopes with pagination and hierarchy' indicate a read-only operation that retrieves and displays information without modification or side effects.
Attacks that exploit this kind of access
List scopes with pagination and hierarchy. It is categorised as a Read tool in the MCP Associative Memory Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Associative Memory Server MCP server in PolicyLayer and add a rule for scope_list: 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 Associative Memory Server. Nothing to install.
scope_list 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 scope_list 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 scope_list. 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.
scope_list is provided by the MCP Associative Memory Server MCP server (mako10k/mcp-assoc-memory). 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 →