AI agents call get_scan_rotation 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.
The 'get_' prefix strongly indicates a query/retrieval operation with no side effects. Reading microscope settings like scan rotation has minimal risk—it only exposes metadata about the instrument's current state without modifying any parameters or performing destructive actions. The confidence is slightly reduced due to the empty description, but the naming pattern provides sufficient evidence for classification.
From the tool's definition Tool name 'get_scan_rotation' uses the 'get' verb, indicating a read operation that retrieves the current scan rotation parameter.
Attacks that exploit this kind of access
get_scan_rotation. 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_scan_rotation: 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_scan_rotation 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_scan_rotation 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_scan_rotation. 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_scan_rotation 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 →