start_circulation
A execute tool on the Pypi:labmcp Alicat MCP server.
This record as markdown: /tools/lab-instrument-mcps/start-circulation.md
What start_circulation does on Pypi:labmcp Alicat
AI agents invoke start_circulation 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.
Why start_circulation is rated High
Starts active circulation system in lab equipment; irreversible state change with potential sample/system damage risk.
From the tool's definition start_circulation on lab instrument; uninformative description
Attacks that exploit this kind of access
The rule that runs start_circulation 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 start_circulation, this is the rule to start with:
start_circulation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pypi:labmcp Alicat, apply this rule, and every start_circulation call is checked against it from then on.
Questions about start_circulation
start_circulation 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.
Register the Pypi:labmcp Alicat MCP server in PolicyLayer and add a rule for start_circulation: 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.
start_circulation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_circulation 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 start_circulation. 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.
start_circulation 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.
More on Pypi:labmcp Alicat, and thousands of servers like it.
Across the catalogue