Get summary information for a thread
AI agents call get_thread_summary to retrieve information from Follow Plan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve and summarize thread information. It has no capability to modify, delete, execute code, or trigger external operations. The lack of parameters that would allow destructive or write operations, combined with the explicit 'Get' verb and 'summary' retrieval nature, places it firmly in the Read category with low severity risk.
From the tool's definition Tool name 'get_thread_summary' and description 'Get summary information for a thread' indicate a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
Get summary information for a thread. It is categorised as a Read tool in the Follow Plan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Follow Plan MCP Server MCP server in PolicyLayer and add a rule for get_thread_summary: 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 Follow Plan MCP Server. Nothing to install.
get_thread_summary 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_thread_summary 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_thread_summary. 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_thread_summary is provided by the Follow Plan MCP Server MCP server (vibeclasses/follow-plan-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 →