query_sql
A execute tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/query-sql.md
What query_sql does on Mapi Agent Memory
AI agents invoke query_sql to trigger actions in Mapi Agent Memory. 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_sql is rated High
The name 'query_sql' suggests execution of SQL queries. Given the context of a memory/governance server with tools that apply, modify, and consolidate memory, SQL queries here could involve both read and write/destructive operations (e.g., SELECT, INSERT, UPDATE, DELETE, DROP). Since arbitrary SQL execution can include destructive or data-modifying statements, Execute is the most appropriate category.
From the tool's definition Tool name is 'query_sql'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs query_sql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_sql, this is the rule to start with:
query_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every query_sql call is checked against it from then on.
Questions about query_sql
query_sql is a execute tool on the Mapi Agent Memory MCP server. It is categorised as a Execute tool in the Mapi Agent Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for query_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 Mapi Agent Memory. Nothing to install.
query_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_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_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_sql is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
Across the catalogue