create_script_tag

THE RISK

High Risk

Why create_script_tag needs a policy

This tool injects JavaScript into a live storefront, which constitutes code execution in the browser context of all visitors. Misuse could lead to XSS attacks, data exfiltration, or malicious scripts being served to customers — high blast radius.

From the tool's definition Inject a new JavaScript file into the storefront

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

POLICY

How to control create_script_tag

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_script_tag": {
      "limits": [
        {
          "counter": "create_script_tag_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

create_script_tag stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Sapo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sapo tools

Financial create_order_transaction Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Tra Execute send_draft_order_invoice Send an invoice email for a draft order. Side effect: sends email to customer; draft statu Write adjust_inventory_level Adjust inventory level by a relative delta (positive = receive stock, negative = remove st Write add_customer_address Add a new address to a customer. Required: address1, city, country. Write complete_draft_order Complete a draft order and convert it into a real order. Side effect: creates an Order fro Write connect_inventory_level Connect an inventory item to a location (enable tracking at that location). For store owne Write create_article Create a new article within a blog. For SEO/content team: provide title, HTML body, Write create_blog Create a new blog. For SEO/content team: set title, handle (URL slug),

All 93 Sapo tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Sapo → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_script_tag

What does the create_script_tag tool do? +

Inject a new JavaScript file into the storefront. For SEO/content team:. It is categorised as a Execute tool in the Sapo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_script_tag? +

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

What risk level is create_script_tag? +

create_script_tag is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_script_tag? +

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

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

create_script_tag is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sapo tool call.

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

CHECK YOUR STACK →