get_cause_info
AI agents call get_cause_info to retrieve information from Decoder 3am without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or fetches information about causes in a knowledge base without creating, modifying, deleting, or executing external operations. The empty description lowers confidence slightly, but the sibling tool names and server purpose (identifying/classifying causes) strongly indicate Read category semantics.
From the tool's definition Tool name 'get_cause_info' and server description indicate this retrieves information about sleep disruption causes from The Longevity Vault's framework.
Attacks that exploit this kind of access
get_cause_info. It is categorised as a Read tool in the Decoder 3am MCP Server, which means it retrieves data without modifying state.
Register the Decoder 3am MCP server in PolicyLayer and add a rule for get_cause_info: 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 Decoder 3am. Nothing to install.
get_cause_info 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_cause_info 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_cause_info. 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_cause_info is provided by the Decoder 3am MCP server (thelongevityvault/decoder-3am-mcp). 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 →