Check if a price feed is stale or unhealthy
AI agents call check_price_feed_health 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 and reads the state of a price feed without creating, modifying, or deleting data. It has no side effects beyond fetching information. While the BNB Chain ecosystem involves financial assets, this specific tool is purely observational—checking health status is a read operation, not a financial transaction or value transfer.
From the tool's definition 'Check if a price feed is stale or unhealthy' — this is a query/diagnostic operation that retrieves the health status of a price feed. The verb 'check' indicates data retrieval with no modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access check_price_feed_health 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 check_price_feed_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_price_feed_health": {}
}
} check_price_feed_health 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 price feed is stale or unhealthy. 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 check_price_feed_health: 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.
check_price_feed_health 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 check_price_feed_health 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 check_price_feed_health. 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.
check_price_feed_health 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.