Check the delivery status of a previously sent postcard.
AI agents call check_status to retrieve information from Postcardbot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the delivery status of an existing postcard. It performs no side effects, does not create, modify, or delete data, and does not execute code or commit financial transactions. It is a pure information retrieval operation, making it a Read category tool with low severity.
From the tool's definition Tool name 'check_status' and description 'Check the delivery status of a previously sent postcard' indicate a read-only query operation that retrieves status information without modifying or creating any data.
Attacks that exploit this kind of access
Check the delivery status of a previously sent postcard. It is categorised as a Read tool in the Postcardbot MCP Server, which means it retrieves data without modifying state.
Register the Postcardbot MCP server in PolicyLayer and add a rule for check_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 Postcardbot. Nothing to install.
check_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 check_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 check_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.
check_status is provided by the Postcardbot MCP server (postcardbot/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 →