AI agents call get_beam_shift to retrieve information from mcpXL30 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to query or retrieve the current beam shift parameters of the ESEM microscope. The 'get_' prefix is strongly associated with Read operations that have no side effects. Even if misused by an agent, retrieving beam shift data poses minimal risk—it does not modify instrument settings, execute commands, or trigger physical movements.
From the tool's definition Tool name 'get_beam_shift' uses the 'get' prefix, indicating a retrieval operation. The sibling tools (get_brightness, get_contrast, get_detector, get_databar_text, etc.) are all Read operations that query microscope state without modification.
Attacks that exploit this kind of access
get_beam_shift. It is categorised as a Read tool in the mcpXL30 MCP Server, which means it retrieves data without modifying state.
Register the mcpXL30 MCP server in PolicyLayer and add a rule for get_beam_shift: 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.
get_beam_shift 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_beam_shift 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_beam_shift. 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_beam_shift 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.
get_beam_shift is one line of mcpXL30's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →