This record as markdown: /tools/io-github-portel-dev-ncp/query.md
What query does on Ncp
AI agents invoke query to trigger actions in Ncp. 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.
Why query is rated High
This tool runs arbitrary SQL against a SQLite database. While named 'query', it explicitly states it executes SQL, which could include SELECT (Read), INSERT/UPDATE (Write), or even DROP/DELETE (Destructive). Since the tool permits arbitrary SQL without stated restrictions, it must be classified at the most severe plausible level short of confirmed destructive operations.
From the tool's definition "Execute a SQL query on the SQLite database" — the word 'Execute' combined with arbitrary SQL query capability
Attacks that exploit this kind of access
The rule that runs query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query, this is the rule to start with:
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 Ncp, apply this rule, and every query call is checked against it from then on.
Questions about query
Execute a SQL query on the SQLite database. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ncp MCP server in PolicyLayer and add a rule for 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 Ncp. Nothing to install.
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 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 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.
query is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue