set_beam_shift · mcpXL30 MCP: Risk & Policy

WHAT IT DOES

What set_beam_shift does on mcpXL30

AI agents use set_beam_shift to create or update resources in mcpXL30 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your mcpXL30 environment.

WHY IT NEEDS A POLICY

Why set_beam_shift needs a policy

Based on the naming convention 'set_*', this tool likely modifies the beam shift parameter on the Philips XL30 ESEM microscope. The sibling tool 'get_beam_shift' reads the current beam shift, so 'set_beam_shift' almost certainly writes/updates it. Adjusting beam shift on an electron microscope affects imaging alignment and could disrupt ongoing experiments or damage samples if misused, warranting a high severity.

From the tool's definition Tool name 'set_beam_shift'; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_beam_shift Rate-limited

set_beam_shift stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_beam_shift": {
      "limits": [
        {
          "counter": "set_beam_shift_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches mcpXL30, so you can run agents against it safely.

FAQ

Questions about set_beam_shift

What does the set_beam_shift tool do? +

set_beam_shift. It is categorised as a Write tool in the mcpXL30 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_beam_shift? +

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

What risk level is set_beam_shift? +

set_beam_shift is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_beam_shift? +

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

How do I block set_beam_shift completely? +

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

What MCP server provides set_beam_shift? +

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

// THE FULL RECORD

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