AI agents invoke calibrate_query to trigger actions in Excel. 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.
The server description explicitly mentions SQL support and the sibling tools include schema/table calibration tools suggesting a query execution context. 'calibrate_query' likely executes SQL or query operations against Excel data. Given the server supports SQL and the tool name implies running a query, Execute is the most appropriate category. Empty description lowers confidence significantly.
From the tool's definition Tool name 'calibrate_query' on a server that supports SQL operations and cross-sheet operations; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access calibrate_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excel, and nothing reaches the server without passing your rules. This is the rule we recommend for calibrate_query:
{
"version": "1",
"default": "deny",
"tools": {
"calibrate_query": {
"limits": [
{
"counter": "calibrate_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}calibrate_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.
calibrate_query. It is categorised as a Execute tool in the Excel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Excel MCP server in PolicyLayer and add a rule for calibrate_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 Excel. Nothing to install.
calibrate_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 calibrate_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 calibrate_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.
calibrate_query is provided by the Excel MCP server (tangentdomain/excel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Excel, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Excel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.