Medium Risk

create_order

Create a SIIL Ostomy order and get a payment link. Creates a WooCommerce order (pending payment) and generates a Stripe or PayPal payment link for the customer to complete payment. Args: line_items: List of items. Each item: {"product_id": 12345, "quantity": 1, "variation_id": 0} billing_first_na...

Risk signalsHigh parameter count (16 properties)

Part of the SIIL Ostomy Store server.

create_order can modify SIIL Ostomy Store data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SIIL OSTOMY STORE →

Free to start. No card required.

AI agents use create_order to create or modify resources in SIIL Ostomy Store. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_order repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SIIL Ostomy Store.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

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

See the full SIIL Ostomy Store policy for all 8 tools.

Get this rule live on your own SIIL Ostomy Store server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SIIL OSTOMY STORE →

These attack patterns abuse exactly the kind of access create_order gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_order only ever does what you allow.

SECURE SIIL OSTOMY STORE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_order tool do? +

Create a SIIL Ostomy order and get a payment link. Creates a WooCommerce order (pending payment) and generates a Stripe or PayPal payment link for the customer to complete payment. Args: line_items: List of items. Each item: {"product_id": 12345, "quantity": 1, "variation_id": 0} billing_first_name: Customer first name billing_last_name: Customer last name billing_email: Customer email address billing_address: Street address billing_city: City billing_postcode: Postal/ZIP code billing_country: ISO 2-letter country code (e.g. "US", "DE", "FR") billing_phone: Phone number (optional) billing_state: State/province (optional) shipping_address: Shipping street (defaults to billing if empty) shipping_city: Shipping city (defaults to billing if empty) shipping_postcode: Shipping postal code (defaults to billing if empty) shipping_country: Shipping country (defaults to billing if empty) payment_method: "stripe" (default) or "paypal" customer_note: Optional note for the order. It is categorised as a Write tool in the SIIL Ostomy Store 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_order? +

Register the SIIL Ostomy Store MCP server in PolicyLayer and add a rule for create_order: 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 SIIL Ostomy Store. Nothing to install.

What risk level is create_order? +

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

Can I rate-limit create_order? +

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

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

create_order is provided by the SIIL Ostomy Store MCP server (hola-ps65/siil-ostomy-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SIIL Ostomy Store tool call.

Deterministic rules across all 8 SIIL Ostomy Store tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.