start-clarification

THE RISK

Low Risk

Why start-clarification needs a policy

This tool starts a clarification conversation to gather requirements or understanding about a project. It does not read data from a system, write or modify data, execute code, delete anything, or move money. It initiates an interactive dialogue process, which is a meta/orchestration action that fits best in 'Other'. Severity is low as misuse would at most trigger an unnecessary conversation flow.

From the tool's definition 'Start a project clarification process' — initiates a conversational/dialogue workflow

Documented attack patterns abuse exactly the kind of access start-clarification gives an agent:

POLICY

How to control start-clarification

PolicyLayer is an MCP gateway — it sits between your AI agents and VibeCoding System, and nothing reaches the server without passing your rules. This is the rule we recommend for start-clarification:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start-clarification": {
      "limits": [
        {
          "counter": "start-clarification_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

start-clarification gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register VibeCoding System — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VibeCoding System tools

Execute deploy-service Deploy application to specified environment Execute performance-test Run performance tests and benchmarks Execute run-tests Execute test suites and return detailed results Execute rollback-deployment Rollback to previous deployment version Write configure-alerts Set up alerts and notifications for system events Write create-api-docs Generate API documentation from code annotations Write generate-code Generate code based on requirements and specifications Write generate-docs Generate comprehensive documentation from code

All 24 VibeCoding System tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about start-clarification

What does the start-clarification tool do? +

Start a project clarification process. It is categorised as a Other tool in the VibeCoding System MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on start-clarification? +

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

What risk level is start-clarification? +

start-clarification is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit start-clarification? +

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

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

start-clarification is provided by the VibeCoding System MCP server (zenobia000/vibecoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VibeCoding System tool call.

Start from VibeCoding System, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →