generate_epic_import
AI agents use generate_epic_import 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.
An AI agent can call generate_epic_import faster than any human can review — one bad instruction and it creates or modifies resources in Carrier Accounting MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
generate_epic_import. 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 generate_epic_import: 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.
generate_epic_import 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 generate_epic_import 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 generate_epic_import. 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.
generate_epic_import 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 →