Get replies to a specific message
AI agents call get_replies 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 retrieves existing message replies without creating, modifying, or deleting data. It is a straightforward query operation that returns information about message threads. No side effects or state changes result from its use, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'get_replies' and description 'Get replies to a specific message' indicate a retrieval operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Get replies to a specific message. 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_replies: 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_replies 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_replies 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_replies. 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_replies 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.
get_replies is one line of Follow Plan MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →