Get Dripper configuration parameters including drip duration, rate limits, and governance settings.
AI agents call dripper_get_config 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 performs a simple data retrieval operation. It queries and returns Dripper configuration settings (drip duration, rate limits, governance settings) with no side effects, state changes, or ability to execute code or modify data. This is a straightforward read operation with minimal security risk even if misused by an agent.
From the tool's definition Tool name 'dripper_get_config' uses the 'get' verb and description states it retrieves 'configuration parameters' without any indication of modification, deletion, or execution of operations.
Documented attack patterns abuse exactly the kind of access dripper_get_config 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 dripper_get_config:
{
"version": "1",
"default": "deny",
"tools": {
"dripper_get_config": {}
}
}dripper_get_config 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.
Get Dripper configuration parameters including drip duration, rate limits, and governance settings. 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 dripper_get_config: 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.
dripper_get_config 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 dripper_get_config 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 dripper_get_config. 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.
dripper_get_config 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.