AI agents call calibrate_tables to retrieve information from Excel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves metadata about tables (names and row counts) from the calibration database. It performs a read/list operation with no side effects, modifications, or destructive actions.
From the tool's definition 列出校准数据库中的所有表及其行数 (Lists all tables in the calibration database and their row counts)
Documented attack patterns abuse exactly the kind of access calibrate_tables 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_tables:
{
"version": "1",
"default": "deny",
"tools": {
"calibrate_tables": {}
}
}calibrate_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出校准数据库中的所有表及其行数. It is categorised as a Read tool in the Excel MCP Server, which means it retrieves data without modifying state.
Register the Excel MCP server in PolicyLayer and add a rule for calibrate_tables: 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_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the calibrate_tables 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_tables. 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_tables 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.