Low Risk

unwatch_project

Stop watching a project for file changes.

Part of the Vibe Hnindex MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call unwatch_project to retrieve information from Vibe Hnindex without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though unwatch_project only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-andyanh174-vibe-hnindex.yaml
tools:
  unwatch_project:
    rules:
      - action: allow

See the full Vibe Hnindex policy for all 21 tools.

Tool Name unwatch_project
Category Read
Risk Level Low

View all 21 tools →

Agents calling read-class tools like unwatch_project have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the unwatch_project tool do? +

Stop watching a project for file changes.. It is categorised as a Read tool in the Vibe Hnindex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on unwatch_project? +

Add a rule in your Intercept YAML policy under the tools section for unwatch_project. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vibe Hnindex MCP server.

What risk level is unwatch_project? +

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

Can I rate-limit unwatch_project? +

Yes. Add a rate_limit block to the unwatch_project rule in your Intercept 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 unwatch_project completely? +

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

unwatch_project is provided by the Vibe Hnindex MCP server (vibe-hnindex). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Vibe Hnindex

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.