AI agents call get_context_history to retrieve information from CoordMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information to support multi-agent coordination. No side effects are indicated by the name. The empty description reduces confidence, but the naming pattern and server purpose (tracking decisions, maintaining consistency) strongly suggest read-only access to stored context. Classified as Read with low severity since context history access poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_context_history' indicates retrieval of historical context data. The description is empty, but the name and server context (coordination/shared memory) suggest this queries past session or decision history without modifying it.
Attacks that exploit this kind of access
get_context_history. It is categorised as a Read tool in the CoordMCP MCP Server, which means it retrieves data without modifying state.
Register the Coord MCP server in PolicyLayer and add a rule for get_context_history: 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 CoordMCP. Nothing to install.
get_context_history 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 get_context_history 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 get_context_history. 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.
get_context_history is provided by the Coord MCP server (siddiquesahabaj/coordmcp). 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 →