Show the active near-hydra configuration: network, account, MPC contract, RPC endpoints. Read-only.
AI agents call hydra_config_show to retrieve information from Near Hydra without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and displays existing configuration state. It performs no mutations, no code execution, no financial transactions, and no destructive operations. The explicit 'Read-only' label and the nature of configuration retrieval—which has no side effects—places it firmly in the Read category with low severity.
From the tool's definition Tool name 'hydra_config_show' and description explicitly states 'Read-only' and retrieves configuration data (network, account, MPC contract, RPC endpoints) without modification.
Documented attack patterns abuse exactly the kind of access hydra_config_show gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Near Hydra, and nothing reaches the server without passing your rules. This is the rule we recommend for hydra_config_show:
{
"version": "1",
"default": "deny",
"tools": {
"hydra_config_show": {}
}
}hydra_config_show 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.
Show the active near-hydra configuration: network, account, MPC contract, RPC endpoints. Read-only. It is categorised as a Read tool in the Near Hydra MCP Server, which means it retrieves data without modifying state.
Register the Near Hydra MCP server in PolicyLayer and add a rule for hydra_config_show: 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 Near Hydra. Nothing to install.
hydra_config_show 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 hydra_config_show 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 hydra_config_show. 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.
hydra_config_show is provided by the Near Hydra MCP server (nikshepsvn/near-hydra). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Near Hydra, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Near Hydra tools catalogued and risk-classified — across an index of 43,000+ MCP servers.