AI agents use package_add_test 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.
The tool name indicates a write operation (package_add_*) that creates or modifies test data within a package context. While the description is empty, reducing confidence slightly, the naming pattern 'add' consistently maps to write operations. In a security data pipeline context, adding tests could modify package behavior or validation rules.
From the tool's definition Tool name 'package_add_test' suggests adding or creating test data/configuration to a package. The 'add' verb indicates a write operation that modifies package state.
Documented attack patterns abuse exactly the kind of access package_add_test gives an agent:
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_add_test:
{
"version": "1",
"default": "deny",
"tools": {
"package_add_test": {
"limits": [
{
"counter": "package_add_test_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}package_add_test 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.
Free to start. No card required.
package_add_test. 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.
Register the Tenzir MCP Server MCP server in PolicyLayer and add a rule for package_add_test: 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.
package_add_test is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the package_add_test 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.
Set action: deny in the PolicyLayer policy for package_add_test. 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.
package_add_test 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.
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.