AI agents call get_specimen_current_detector_mode 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 retrieves the current detector mode setting of the ESEM microscope specimen chamber. It queries state information with no side effects, aligning with the Read category. The empty description reduces confidence slightly, but the naming convention and context of sibling getter tools strongly indicate this is a read-only query operation.
From the tool's definition Tool name 'get_specimen_current_detector_mode' uses the 'get_' prefix, indicating a retrieval operation. The sibling tools on this server include other 'get_' prefixed tools (get_area_dot_shift, get_beam_shift, get_brightness, get_contrast, get_databar_text)…
Attacks that exploit this kind of access
get_specimen_current_detector_mode. 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_specimen_current_detector_mode: 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_specimen_current_detector_mode 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_specimen_current_detector_mode 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_specimen_current_detector_mode. 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_specimen_current_detector_mode 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 →