AI agents invoke execute_query to trigger actions in 1C MCP Toolkit. 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.
execute_query can run arbitrary database queries whose effects depend on the query argument. Without description clarity on restrictions (e.g., read-only enforcement), this must be treated as Execute. If the tool permits DELETE, DROP, or UPDATE, it could escalate to Destructive; however, given standard semantics, Execute is the appropriate baseline.
From the tool's definition Tool name 'execute_query' in context of 1C:Enterprise database integration indicates arbitrary query execution against a database.
Documented attack patterns abuse exactly the kind of access execute_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1C MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_query": {
"limits": [
{
"counter": "execute_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_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.
Free to start. No card required.
execute_query. It is categorised as a Execute tool in the 1C MCP Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1C MCP Toolkit MCP server in PolicyLayer and add a rule for execute_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 1C MCP Toolkit. Nothing to install.
execute_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 execute_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 execute_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.
execute_query is provided by the 1C MCP Toolkit MCP server (roctup/1c-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 1C MCP Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 1C MCP Toolkit tools catalogued and risk-classified — across an index of 42,500+ MCP servers.