AI agents invoke load_pipeline to trigger actions in MaaMCP. 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.
Based on the server context (MaaFramework automation) and sibling tools like 'clear_pipeline_resources', 'connect_adb_device', and 'connect_window', a 'load_pipeline' tool likely loads an automation pipeline configuration or resource set, which could trigger execution of automation scripts or workflows. This falls under Execute as it likely initiates or prepares an operational pipeline.
From the tool's definition Tool name 'load_pipeline' on a server providing Android/Windows automation capabilities; description is empty and uninformative.
Attacks that exploit this kind of access
load_pipeline. It is categorised as a Execute tool in the MaaMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maa MCP server in PolicyLayer and add a rule for load_pipeline: 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 MaaMCP. Nothing to install.
load_pipeline 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 load_pipeline 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 load_pipeline. 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.
load_pipeline is provided by the Maa MCP server (maa-ai/maamcp). 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 →