Launch an new microsoft excel application or use the existed one.
AI agents call ScreenShot to retrieve information from OfficeMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A screenshot tool retrieves visual data from the screen without altering system state, modifying data, or executing arbitrary code. While the description is inaccurate/misleading, the tool name strongly indicates a passive data retrieval function. Confidence is slightly reduced due to the description mismatch, but screenshot capture is fundamentally a Read operation.
From the tool's definition Tool name is 'ScreenShot' which captures screen display without modification. The description appears to be incorrect/mismatched (describes launching Excel rather than taking a screenshot), but the tool name clearly indicates a read-only capture operation.
Documented attack patterns abuse exactly the kind of access ScreenShot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OfficeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ScreenShot:
{
"version": "1",
"default": "deny",
"tools": {
"ScreenShot": {}
}
}ScreenShot 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.
Launch an new microsoft excel application or use the existed one. It is categorised as a Read tool in the OfficeMCP MCP Server, which means it retrieves data without modifying state.
Register the Office MCP server in PolicyLayer and add a rule for ScreenShot: 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 OfficeMCP. Nothing to install.
ScreenShot 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 ScreenShot 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 ScreenShot. 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.
ScreenShot is provided by the Office MCP server (officemcp/officemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 OfficeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 OfficeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.