AI agents use calibrate_import to create or update resources in Excel — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excel environment.
Given the server's purpose of manipulating Excel files and the naming pattern of sibling tools that create, modify, and delete data, 'calibrate_import' most likely performs a reversible write operation (importing or transforming data). The empty description reduces confidence, but the context strongly suggests Write rather than Read or Execute.
From the tool's definition Tool name 'calibrate_import' appears to modify/import data; sibling tools include 'excel_create_file', 'excel_create_sheet', 'excel_delete_columns', 'excel_delete_rows', and 'excel_convert_format', indicating this server performs reversible data modifications.
Documented attack patterns abuse exactly the kind of access calibrate_import 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_import:
{
"version": "1",
"default": "deny",
"tools": {
"calibrate_import": {
"limits": [
{
"counter": "calibrate_import_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}calibrate_import stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
calibrate_import. It is categorised as a Write tool in the Excel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excel MCP server in PolicyLayer and add a rule for calibrate_import: 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_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calibrate_import 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_import. 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_import 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.