Check if a token is allowed for swapping in the Yield Reserve. Tokens can be enabled as source (input) or destination (output) tokens.
AI agents call yield_reserve_check_token_permission 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.
This tool retrieves or queries the permission status of a token within the Yield Reserve system. It performs a read-only lookup to determine whether a token can be used as a source or destination in swaps, but does not create, modify, execute code, delete data, or move funds. The low severity reflects minimal risk if misused by an agent—it merely returns permission information.
From the tool's definition Tool name 'yield_reserve_check_token_permission' and description 'Check if a token is allowed for swapping' indicates a query/lookup operation.
Documented attack patterns abuse exactly the kind of access yield_reserve_check_token_permission 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 yield_reserve_check_token_permission:
{
"version": "1",
"default": "deny",
"tools": {
"yield_reserve_check_token_permission": {}
}
}yield_reserve_check_token_permission 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.
Check if a token is allowed for swapping in the Yield Reserve. Tokens can be enabled as source (input) or destination (output) tokens. 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 yield_reserve_check_token_permission: 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.
yield_reserve_check_token_permission 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 yield_reserve_check_token_permission 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 yield_reserve_check_token_permission. 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.
yield_reserve_check_token_permission 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.