post_to_epic · Carrier Accounting MCP: Risk & Policy

WHAT IT DOES

What post_to_epic does on Carrier Accounting MCP

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

WHY IT NEEDS A POLICY

Why post_to_epic needs a policy

This tool commits approved transactions to an accounting system of record, which is a reversible but consequential data modification. It does not move money directly (hence not Financial) nor does it delete data (hence not Destructive), but it does persist financial records that affect accounting state.

From the tool's definition Tool name 'post_to_epic' combined with description 'Post all approved transactions from a run to Applied Epic via REST API' indicates the tool creates/modifies financial records in an external accounting system (Applied Epic).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

post_to_epic Rate-limited

post_to_epic 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": {
    "post_to_epic": {
      "limits": [
        {
          "counter": "post_to_epic_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 Carrier Accounting MCP, so you can run agents against it safely.

FAQ

Questions about post_to_epic

What does the post_to_epic tool do? +

Post all approved transactions from a run to Applied Epic via REST API. It is categorised as a Write tool in the Carrier Accounting 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 post_to_epic? +

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

What risk level is post_to_epic? +

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

Can I rate-limit post_to_epic? +

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

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

post_to_epic is provided by the Carrier Accounting MCP server (pramodmisra/carrier-accounting-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.