Analyze a token contract for security risks and red flags
AI agents call analyze_token_security to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static analysis of token contract code to identify security issues. This is a read-only operation that queries contract information and returns risk assessment results. It has no side effects, does not execute code on-chain, does not modify data, and does not move funds.
From the tool's definition Tool name is 'analyze_token_security' and description states it 'Analyze a token contract for security risks and red flags' — this is a query/analysis operation that retrieves and examines data about a contract without modifying state or executing…
Documented attack patterns abuse exactly the kind of access analyze_token_security gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_token_security:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_token_security": {}
}
}analyze_token_security is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze a token contract for security risks and red flags. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for analyze_token_security: 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 BNB Chain MCP. Nothing to install.
analyze_token_security 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 analyze_token_security 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 analyze_token_security. 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.
analyze_token_security is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.