Medium Risk

package_create

package_create

How to control package_create ↓

What package_create does on Tenzir MCP Server

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

Medium Risk

Why package_create needs a policy

The 'package_create' action creates or registers new packages within Tenzir's security data processing framework. This is a reversible data creation operation (packages can be modified or removed) that modifies the state of the system but does not execute arbitrary code, delete data, or move resources.

From the tool's definition Tool name 'package_create' indicates creation of a new package. The server context involves security data pipelines and OCSF mapping. Description is empty, limiting specificity.

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

How to control package_create

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

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

package_create 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 Tenzir MCP Server — 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 package_create

What does the package_create tool do? +

package_create. It is categorised as a Write tool in the Tenzir MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on package_create? +

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

What risk level is package_create? +

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

Can I rate-limit package_create? +

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

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

package_create is provided by the Tenzir MCP Server MCP server (tenzir/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tenzir MCP Server tool call.

Start from Tenzir MCP Server, 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.

15 Tenzir MCP Server 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.