run_full_pipeline · Meeting Automation MCP Server MCP

WHAT IT DOES

What run_full_pipeline does on Meeting Automation MCP Server

AI agents invoke run_full_pipeline to trigger actions in Meeting Automation MCP Server. 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 IT NEEDS A POLICY

Why run_full_pipeline needs a policy

This tool likely orchestrates a sequence of operations across multiple integrated services (meeting extraction, task creation, documentation). While the empty description reduces confidence, the context indicates it executes complex workflows with potential side effects on Asana tasks and Notion documents.

From the tool's definition Tool name 'run_full_pipeline' combined with server description stating it 'orchestrates Fireflies, Asana, and Notion MCP servers to automate end-to-end meeting workflows.' The sibling tools include both write operations (create_meeting_task,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_full_pipeline Rate-limited

run_full_pipeline 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_full_pipeline": {
      "limits": [
        {
          "counter": "run_full_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about run_full_pipeline

What does the run_full_pipeline tool do? +

run_full_pipeline. It is categorised as a Execute tool in the Meeting Automation MCP Server 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_full_pipeline? +

Register the Meeting Automation MCP Server MCP server in PolicyLayer and add a rule for run_full_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 Meeting Automation MCP Server. Nothing to install.

What risk level is run_full_pipeline? +

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

Can I rate-limit run_full_pipeline? +

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

How do I block run_full_pipeline completely? +

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

What MCP server provides run_full_pipeline? +

run_full_pipeline is provided by the Meeting Automation MCP Server MCP server (ramhori/meeting-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.