post_to_epic_via_browser
AI agents use post_to_epic_via_browser 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.
The tool POSTs data to a live accounting system (Applied Epic). While the server description mentions safety features like trial mode and human review queues, the actual tool lacks description, suggesting it may bypass guardrails. POSTing to accounting systems is Write (creates transaction records) rather than Destructive (no deletion).
From the tool's definition Tool name is 'post_to_epic_via_browser' indicating it posts (writes) data to Applied Epic, a financial/accounting system.
Attacks that exploit this kind of access
post_to_epic_via_browser. 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.
Register the Carrier Accounting MCP server in PolicyLayer and add a rule for post_to_epic_via_browser: 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.
post_to_epic_via_browser is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the post_to_epic_via_browser 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 post_to_epic_via_browser. 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.
post_to_epic_via_browser 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.
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 →