Get the used range (bounding rectangle of all cells with data) for a worksheet
AI agents call excel_get_used_range to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries the dimensions of used cells in an Excel worksheet. It retrieves information about data boundaries but does not create, modify, delete, or execute any operations. The operation has minimal blast radius—it cannot cause financial harm, data loss, or unintended external effects. The user gains visibility into spreadsheet structure only.
From the tool's definition Tool name 'excel_get_used_range' and description 'Get the used range (bounding rectangle of all cells with data) for a worksheet' indicate a query operation that retrieves metadata about worksheet structure without modifying, executing, or deleting data.
Documented attack patterns abuse exactly the kind of access excel_get_used_range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for excel_get_used_range:
{
"version": "1",
"default": "deny",
"tools": {
"excel_get_used_range": {}
}
}excel_get_used_range 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.
Get the used range (bounding rectangle of all cells with data) for a worksheet. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for excel_get_used_range: 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 Sage MCP. Nothing to install.
excel_get_used_range 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 excel_get_used_range 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 excel_get_used_range. 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.
excel_get_used_range is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.