Medium Risk

create_ticket

Open a support ticket / human handoff for a contact

How to control create_ticket ↓

What create_ticket does on Mcp Afip

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

Medium Risk

Why create_ticket needs a policy

This tool creates a new support ticket, which is a reversible write operation. It adds data to a support system but does not execute code, delete data, or involve financial transactions. The severity is low because ticket creation has minimal blast radius—it creates a record that can be reviewed, cancelled, or deleted by support staff.

From the tool's definition Tool name 'create_ticket' and description 'Open a support ticket / human handoff for a contact' indicate creation of a new support record.

Documented attack patterns abuse exactly the kind of access create_ticket gives an agent:

How to control create_ticket

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for create_ticket:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_ticket": {
      "limits": [
        {
          "counter": "create_ticket_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_ticket 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.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_ticket

What does the create_ticket tool do? +

Open a support ticket / human handoff for a contact. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_ticket? +

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

What risk level is create_ticket? +

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

Can I rate-limit create_ticket? +

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

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

create_ticket is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.