AI agents invoke auto_focus to trigger actions in mcpXL30. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Auto-focus on an electron microscope involves adjusting the beam focus, which is an active operation affecting the electron beam and potentially the sample. While not explicitly destructive, improper focus adjustment in an ESEM context could affect beam parameters (high tension, beam shift) and interact with sensitive hardware. The description is empty, lowering confidence.
From the tool's definition Tool name 'auto_focus' on a server that controls a Philips XL30 ESEM microscope with tools for imaging, beam adjustment, and vacuum chamber operations.
Attacks that exploit this kind of access
auto_focus. It is categorised as a Execute tool in the mcpXL30 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the mcpXL30 MCP server in PolicyLayer and add a rule for auto_focus: 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 mcpXL30. Nothing to install.
auto_focus is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the auto_focus 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 auto_focus. 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.
auto_focus is provided by the mcpXL30 MCP server (tspspi/mcpxl30). 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 →