maasy_execute_action · Maasy — AI Marketing Copilot MCP

WHAT IT DOES

What maasy_execute_action does on Maasy — AI Marketing Copilot

AI agents invoke maasy_execute_action to trigger actions in Maasy — AI Marketing Copilot. 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 maasy_execute_action needs a policy

The tool directly executes arbitrary copilot actions rather than merely retrieving or modifying data through a fixed schema. 'Redistribute budget' crosses into financial territory (high severity), but the tool's primary risk is as an Execute category because it triggers external operations whose effects are contingent on user-supplied action parameters.

From the tool's definition Tool description states 'Execute a copilot action' with examples including 'redistribute budget' and 'rotate creatives' — these are external operations with side effects that depend on the specific action argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

maasy_execute_action Rate-limited

maasy_execute_action 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": {
    "maasy_execute_action": {
      "limits": [
        {
          "counter": "maasy_execute_action_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 Maasy — AI Marketing Copilot, so you can run agents against it safely.

FAQ

Questions about maasy_execute_action

What does the maasy_execute_action tool do? +

Execute a copilot action: generate report, redistribute budget, rotate creatives, diagnose campaigns, etc. It is categorised as a Execute tool in the Maasy — AI Marketing Copilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on maasy_execute_action? +

Register the Maasy — AI Marketing Copilot MCP server in PolicyLayer and add a rule for maasy_execute_action: 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 Maasy — AI Marketing Copilot. Nothing to install.

What risk level is maasy_execute_action? +

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

Can I rate-limit maasy_execute_action? +

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

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

maasy_execute_action is provided by the Maasy — AI Marketing Copilot MCP server (@maasy-ai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.