List all available contexts for categorizing notes
AI agents call list_contexts to retrieve information from Vimango MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply enumerates contexts used for note categorization. It performs a read-only retrieval operation with no side effects, state changes, or destructive capability. The blast radius of misuse is minimal—an agent can only discover what contexts already exist in the database.
From the tool's definition Tool name 'list_contexts' and description 'List all available contexts' indicate a query operation that retrieves existing data without modification.
Attacks that exploit this kind of access
List all available contexts for categorizing notes. It is categorised as a Read tool in the Vimango MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vimango MCP Server MCP server in PolicyLayer and add a rule for list_contexts: 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 Vimango MCP Server. Nothing to install.
list_contexts 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 list_contexts 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 list_contexts. 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.
list_contexts is provided by the Vimango MCP Server MCP server (slzatz/vimango_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 →