create_support_ticket · Acme Operations Assistant MCP

WHAT IT DOES

What create_support_ticket does on Acme Operations Assistant

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

WHY IT NEEDS A POLICY

Why create_support_ticket needs a policy

This tool creates (writes) a new support ticket record, which is a reversible operation. The sibling tools on this server are all read-only (account_summary, get_customer, get_order, list_customer_orders, list_open_tickets, search_customers), and this is the only write operation observed.

From the tool's definition Tool name 'create_support_ticket' combined with description stating it 'Create[s] a new support ticket' indicates creation of a new record with no deletion or code execution involved.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_support_ticket Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_support_ticket": {
      "limits": [
        {
          "counter": "create_support_ticket_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 Acme Operations Assistant, so you can run agents against it safely.

FAQ

Questions about create_support_ticket

What does the create_support_ticket tool do? +

Create a new support ticket (priority: low, medium, high, urgent). It is categorised as a Write tool in the Acme Operations Assistant 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_support_ticket? +

Register the Acme Operations Assistant MCP server in PolicyLayer and add a rule for create_support_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 Acme Operations Assistant. Nothing to install.

What risk level is create_support_ticket? +

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

Can I rate-limit create_support_ticket? +

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

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

create_support_ticket is provided by the Acme Operations Assistant MCP server (yesidevelop/simple-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.