AI agents invoke query_blockchain_sql to trigger actions in Cryo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name and server context, this tool likely executes SQL queries against blockchain data. SQL execution can range from read-only SELECT queries to destructive DDL/DML operations. Sibling tools like 'query_sql' and 'query_dataset' suggest arbitrary query execution. Empty description lowers confidence, but the Execute category is most appropriate given the SQL execution pattern.
From the tool's definition Tool name 'query_blockchain_sql' and server context (sibling tool 'query_sql', SQL-based blockchain data extraction). Description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access query_blockchain_sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cryo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_blockchain_sql:
{
"version": "1",
"default": "deny",
"tools": {
"query_blockchain_sql": {
"limits": [
{
"counter": "query_blockchain_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} query_blockchain_sql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_blockchain_sql. It is categorised as a Execute tool in the Cryo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cryo MCP Server MCP server in PolicyLayer and add a rule for query_blockchain_sql: 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 Cryo MCP Server. Nothing to install.
query_blockchain_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_blockchain_sql 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 query_blockchain_sql. 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.
query_blockchain_sql is provided by the Cryo MCP Server MCP server (z80dev/cryo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Cryo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Cryo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.