New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dismiss_vulnerability

Dismiss a vulnerability with a reason (acceptable_risk, false_positive, used_in_tests, mitigating_control, not_applicable) and optional comment

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/dismiss-vulnerability.md

What dismiss_vulnerability does on Gitlab Mcp

AI agents use dismiss_vulnerability to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.

Why dismiss_vulnerability is rated Medium

Dismissing a vulnerability changes its state in the security tracking system, which could hide real security issues from teams. This is a reversible write operation (vulnerabilities can be re-opened), but misuse could lead to genuine vulnerabilities being ignored. The most severe applicable category is Write since the action modifies vulnerability state rather than deleting data or executing code.

From the tool's definition Dismiss a vulnerability with a reason ... and optional comment

Questions about dismiss_vulnerability

What does the dismiss_vulnerability tool do? +

Dismiss a vulnerability with a reason (acceptable_risk, false_positive, used_in_tests, mitigating_control, not_applicable) and optional comment. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dismiss_vulnerability? +

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

What risk level is dismiss_vulnerability? +

dismiss_vulnerability is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dismiss_vulnerability? +

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

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

dismiss_vulnerability is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

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.