call_tool_verify_all

Runs COMPLETE validation including all checks + performance + E2E for deployment.

Server Superkit superkit-mcp-server
Category Execute
Risk class High
Parameters 42 required

What call_tool_verify_all does on Superkit

AI agents invoke call_tool_verify_all to trigger actions in Superkit. 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.

ParameterTypeRequiredDescription
url string Yes
skipE2E boolean
stopOnFail boolean
projectPath string Yes

Parameters from the server's own tool schema.

Why call_tool_verify_all needs a policy

This tool actively executes a comprehensive suite of validations, performance tests, and end-to-end tests. The word 'Runs' confirms active execution of external operations. Misuse could trigger unintended deployments or resource-intensive test suites, making severity high. It does not appear to delete data or move money, so Execute is the most severe applicable category.

From the tool's definition "Runs COMPLETE validation including all checks + performance + E2E for deployment"

Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets

Questions about call_tool_verify_all

What does the call_tool_verify_all tool do? +

Runs COMPLETE validation including all checks + performance + E2E for deployment. It is categorised as a Execute tool in the Superkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does call_tool_verify_all accept? +

call_tool_verify_all accepts 4 parameters: url, skipE2E, stopOnFail, projectPath. Required: url, projectPath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on call_tool_verify_all? +

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

What risk level is call_tool_verify_all? +

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

Can I rate-limit call_tool_verify_all? +

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

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

call_tool_verify_all is provided by the Superkit MCP server (superkit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.