Check the status of a replay job
AI agents call get_replay_status to retrieve information from RequestBin 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 the status of an existing replay job. It is a read-only operation with no side effects, making it a Read category risk. The severity is low because checking status information poses minimal security risk—it cannot execute code, modify data, delete resources, or initiate financial transactions.
From the tool's definition Tool name 'get_replay_status' and description 'Check the status of a replay job' indicate a query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Check the status of a replay job. It is categorised as a Read tool in the RequestBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RequestBin MCP Server MCP server in PolicyLayer and add a rule for get_replay_status: 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 RequestBin MCP Server. Nothing to install.
get_replay_status 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_replay_status 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_replay_status. 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_replay_status is provided by the RequestBin MCP Server MCP server (requestbin/mcp-server). 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 →