AI agents call get_session_log 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.
The tool retrieves session logs for a coordination/collaboration server. Log retrieval is a read operation with no side effects. Confidence is moderate (0.85) rather than high (0.95) due to the empty description, which leaves some ambiguity about scope, but the name strongly indicates a query/fetch operation. Low severity because reading logs poses minimal risk compared to write, execute, or destructive operations.
From the tool's definition Tool name 'get_session_log' indicates retrieval of log data. No description provided, but naming convention and context within a coordination server for multi-agent collaboration suggests querying session history/records without modification.
Attacks that exploit this kind of access
get_session_log. 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_session_log: 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_session_log 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_session_log 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_session_log. 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_session_log 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 →