ModelRisk: Get the name and path of the active workbook.
AI agents call get_active_workbook to retrieve information from ModelRisk MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval-only operation that fetches the name and file path of an active workbook—classic Read category behavior. No data is modified, no code is executed, and no operations are triggered. The blast radius if misused is minimal; an agent could only learn which workbook is currently open, posing negligible risk. Low severity is appropriate for this informational query.
From the tool's definition Tool name 'get_active_workbook' and description 'Get the name and path of the active workbook' indicate a simple query operation that retrieves metadata about the currently active Excel workbook without modifying, executing code, or causing side effects.
Attacks that exploit this kind of access
ModelRisk: Get the name and path of the active workbook. It is categorised as a Read tool in the ModelRisk MCP MCP Server, which means it retrieves data without modifying state.
Register the ModelRisk MCP server in PolicyLayer and add a rule for get_active_workbook: 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 ModelRisk MCP. Nothing to install.
get_active_workbook 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 get_active_workbook 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 get_active_workbook. 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.
get_active_workbook is provided by the ModelRisk MCP server (vosesoftware/modelrisk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →