Check if a timelock encrypted message is ready for decryption.
AI agents call check_decryption_status to retrieve information from Shutter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about whether a message's timelock has expired, enabling the caller to determine readiness for decryption. It is purely informational with no side effects, reversible operations, code execution, or financial impact. It falls clearly into the Read category.
From the tool's definition The tool 'check_decryption_status' performs a status check on timelock-encrypted messages. The description explicitly states it 'Check[s] if a timelock encrypted message is ready for decryption' — a query operation with no data modification, deletion, or…
Attacks that exploit this kind of access
Check if a timelock encrypted message is ready for decryption. It is categorised as a Read tool in the Shutter MCP MCP Server, which means it retrieves data without modifying state.
Register the Shutter MCP server in PolicyLayer and add a rule for check_decryption_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 Shutter MCP. Nothing to install.
check_decryption_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_decryption_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_decryption_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_decryption_status is provided by the Shutter MCP server (shutter-network/shuttermcp). 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 →