add_revenue · Revenue Engine MCP: Risk & Policy

WHAT IT DOES

What add_revenue does on Revenue Engine MCP

AI agents use add_revenue to create or update resources in Revenue Engine MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revenue Engine MCP environment.

WHY IT NEEDS A POLICY

Why add_revenue needs a policy

This tool creates or adds new financial records (closed deals) to the revenue tracking system, which is a write operation that modifies data reversibly. While it involves financial data, it is not moving money or creating obligations—it is recording already-completed transactions.

From the tool's definition Tool name 'add_revenue' combined with description 'Add a closed deal' indicates creation of a new revenue record in the system. This modifies business-critical financial data by recording completed transactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_revenue Rate-limited

add_revenue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_revenue": {
      "limits": [
        {
          "counter": "add_revenue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about add_revenue

What does the add_revenue tool do? +

Add a closed deal. It is categorised as a Write tool in the Revenue Engine MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_revenue? +

Register the Revenue Engine MCP server in PolicyLayer and add a rule for add_revenue: 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 Revenue Engine MCP. Nothing to install.

What risk level is add_revenue? +

add_revenue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_revenue? +

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

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

add_revenue is provided by the Revenue Engine MCP server (promptishoperations/mcpspec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.