data_query
Run a query (SQL for Postgres/Supabase/SQLite, function path for Convex, REST path for PocketBase/Appwrite).
This record as markdown: /tools/io-github-kivanccakmak-yaver/data-query.md
What data_query does on Yaver
AI agents invoke data_query to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | string | — | JSON args |
query | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why data_query is rated High
This tool executes arbitrary SQL queries and function/REST calls against databases and backends. Because it accepts arbitrary SQL, it can run destructive statements (DROP, DELETE, TRUNCATE) or data-exfiltrating SELECT queries.
From the tool's definition "Run a query (SQL for Postgres/Supabase/SQLite, function path for Convex, REST path for PocketBase/Appwrite)"
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs data_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_query, this is the rule to start with:
data_query 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every data_query call is checked against it from then on.
Questions about data_query
Run a query (SQL for Postgres/Supabase/SQLite, function path for Convex, REST path for PocketBase/Appwrite). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
data_query accepts 3 parameters: args, query, directory. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for data_query: 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 Yaver. Nothing to install.
data_query 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 data_query 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 data_query. 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.
data_query is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue