Run a Postman/Newman collection against API endpoints.
AI agents invoke api_newman_run to trigger actions in Zebbern Kali MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes network operations and API calls whose side effects depend entirely on the contents of the Postman collection and target endpoints provided. An AI agent could use this to invoke arbitrary API actions (create accounts, modify data, trigger workflows, exfiltrate information) against any reachable endpoint.
From the tool's definition Tool name 'api_newman_run' with description 'Run a Postman/Newman collection against API endpoints' indicates execution of HTTP requests against external systems based on provided collection/endpoint arguments.
Documented attack patterns abuse exactly the kind of access api_newman_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for api_newman_run:
{
"version": "1",
"default": "deny",
"tools": {
"api_newman_run": {
"limits": [
{
"counter": "api_newman_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}api_newman_run 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.
Free to start. No card required.
Run a Postman/Newman collection against API endpoints. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for api_newman_run: 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 Zebbern Kali MCP. Nothing to install.
api_newman_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the api_newman_run 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 api_newman_run. 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.
api_newman_run is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.