AI agents use zap.create_context to create or update resources in VulneraMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VulneraMCP environment.
Based on the tool name, this likely creates a new scanning context in OWASP ZAP, which is a Write operation (reversible creation of a configuration object). The empty description lowers confidence. Severity is medium given it could configure attack scopes, but creating a context alone is not destructive.
From the tool's definition Tool name 'zap.create_context' suggests creating a new context in OWASP ZAP; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access zap.create_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VulneraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for zap.create_context:
{
"version": "1",
"default": "deny",
"tools": {
"zap.create_context": {
"limits": [
{
"counter": "zap.create_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zap.create_context 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.
zap.create_context. It is categorised as a Write tool in the VulneraMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vulnera MCP server in PolicyLayer and add a rule for zap.create_context: 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 VulneraMCP. Nothing to install.
zap.create_context 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 zap.create_context 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 zap.create_context. 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.
zap.create_context is provided by the Vulnera MCP server (telmon95/vulneramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 VulneraMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 VulneraMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.