Search tasks, claims, updates, and decisions by free text.
AI agents call coord_search_context to retrieve information from Session Coord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against the session coordination state (tasks, claims, updates, decisions). It retrieves information based on search criteria but does not create, modify, delete, or execute any actions. The 'search' verb and absence of side-effect language confirm it belongs in the Read category, with low severity due to its read-only nature and limited blast radius.
From the tool's definition Tool description explicitly states 'Search tasks, claims, updates, and decisions by free text' — a retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search tasks, claims, updates, and decisions by free text. It is categorised as a Read tool in the Session Coord MCP Server, which means it retrieves data without modifying state.
Register the Session Coord MCP server in PolicyLayer and add a rule for coord_search_context: 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 Session Coord. Nothing to install.
coord_search_context 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 coord_search_context 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 coord_search_context. 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.
coord_search_context is provided by the Session Coord MCP server (lingfeng-vels/session-coord-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 →