get_detector

get_detector

Server mcpXL30 tspspi/mcpxl30
Category Read
Risk class Low
Parameters 00 required

What get_detector does on mcpXL30

AI agents call get_detector 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.

Why get_detector needs a policy

This tool retrieves detector state or configuration information from the microscope without modifying any settings or triggering operations. Read operations on microscope parameters pose minimal risk.

From the tool's definition Tool name 'get_detector' follows the 'get_*' naming pattern consistent with other read-only tools on the server (get_area_dot_shift, get_beam_shift, get_brightness, get_contrast, get_databar_text).

Questions about get_detector

What does the get_detector tool do? +

get_detector. It is categorised as a Read tool in the mcpXL30 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_detector? +

Register the mcpXL30 MCP server in PolicyLayer and add a rule for get_detector: 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.

What risk level is get_detector? +

get_detector is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_detector? +

Yes. Add a rate_limit block to the get_detector 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.

How do I block get_detector completely? +

Set action: deny in the PolicyLayer policy for get_detector. 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.

What MCP server provides get_detector? +

get_detector 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.

// THE FULL RECORD

get_detector 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.