crypto_status
Show local encryption key status (never exposes key material).
This record as markdown: /tools/todos/crypto-status.md
What crypto_status does on Todos
AI agents call crypto_status to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crypto_status is rated Low
This tool retrieves encryption key status information for display purposes only. The explicit note that it 'never exposes key material' confirms it performs no side effects, modifications, or security-sensitive operations.
From the tool's definition Tool name 'crypto_status' and description 'Show local encryption key status (never exposes key material)' indicates a read-only query operation that retrieves status information without modifying, executing, or exposing sensitive cryptographic material.
Attacks that exploit this kind of access
The rule that runs crypto_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_status, this is the rule to start with:
crypto_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every crypto_status call is checked against it from then on.
Questions about crypto_status
Show local encryption key status (never exposes key material). It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for crypto_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 Todos. Nothing to install.
crypto_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 crypto_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 crypto_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.
crypto_status is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue