run_methodscript

A execute tool on the Pypi:labmcp Alicat MCP server.

SERVERPypi:labmcp Alicat SOURCEpypi:labmcp-alicat

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lab-instrument-mcps/run-methodscript.md

WHAT IT DOES

What run_methodscript does on Pypi:labmcp Alicat

AI agents invoke run_methodscript to trigger actions in Pypi:labmcp Alicat. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_methodscript is rated High

Methodscript execution on lab instruments can trigger unpredictable physical operations with significant blast radius.

From the tool's definition uninformative description, methodscript suggests arbitrary code execution

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_methodscript safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:labmcp Alicat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_methodscript, this is the rule to start with:

run_methodscript Rate-limited

run_methodscript stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_methodscript": {
      "limits": [
        {
          "counter": "run_methodscript_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pypi:labmcp Alicat, apply this rule, and every run_methodscript call is checked against it from then on.

FAQ

Questions about run_methodscript

What does the run_methodscript tool do? +

run_methodscript is a execute tool on the Pypi:labmcp Alicat MCP server. It is categorised as a Execute tool in the Pypi:labmcp Alicat MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_methodscript? +

Register the Pypi:labmcp Alicat MCP server in PolicyLayer and add a rule for run_methodscript: 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 Pypi:labmcp Alicat. Nothing to install.

What risk level is run_methodscript? +

run_methodscript is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_methodscript? +

Yes. Add a rate_limit block to the run_methodscript 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 run_methodscript completely? +

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

run_methodscript is provided by the Pypi:labmcp Alicat MCP server (pypi:labmcp-alicat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pypi:labmcp Alicat, and thousands of servers like it.

This server

All 242 Pypi:labmcp Alicat tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →