AI agents call get_lines_per_frame 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 and context within a microscope imaging control system strongly suggest this retrieves a display or imaging configuration parameter (lines per frame in raster scanning). No side effects, no modifications, and no destructive capabilities. The empty description lowers confidence slightly, but the naming convention and peer tools provide sufficient evidence for a Read classification with low severity.
From the tool's definition Tool name 'get_lines_per_frame' indicates a getter/query operation for microscope display parameters; consistent with sibling tools like 'get_beam_shift', 'get_brightness', 'get_contrast' which are all read operations.
Attacks that exploit this kind of access
get_lines_per_frame. 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_lines_per_frame: 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_lines_per_frame 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_lines_per_frame 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_lines_per_frame. 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_lines_per_frame 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 →