Analyze a token contract for rug pull risk and safety signals. Returns honeypot detection, liquidity lock status, ownership concentration, and a risk verdict. Use before swapping into any unfamiliar token.
AI agents call get_token_forensics to retrieve information from Maiat Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure analysis/read tool that examines contract state and returns informational signals. It has no side effects on tokens, wallets, or financial transactions. While it operates in a financial context (analyzing token safety), the tool itself does not move money, execute trades, or modify data—it only gathers and returns risk assessment information to inform the user's decisions.
From the tool's definition The tool 'Analyze a token contract for rug pull risk and safety signals. Returns honeypot detection, liquidity lock status, ownership concentration, and a risk verdict.' performs querying and analysis only.
Attacks that exploit this kind of access
Analyze a token contract for rug pull risk and safety signals. Returns honeypot detection, liquidity lock status, ownership concentration, and a risk verdict. Use before swapping into any unfamiliar token. It is categorised as a Read tool in the Maiat Protocol MCP Server, which means it retrieves data without modifying state.
Register the Maiat Protocol MCP server in PolicyLayer and add a rule for get_token_forensics: 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 Maiat Protocol. Nothing to install.
get_token_forensics 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_token_forensics 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_token_forensics. 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_token_forensics is provided by the Maiat Protocol MCP server (jhinresh/maiat-protocol). 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 →