snyk_test_severity_filter

Ejecuta snyk test filtrando por severidad.

SERVERMCP Framework Personal SOURCEinggerman/mcps

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/snyk-test-severity-filter.md

WHAT IT DOES

What snyk_test_severity_filter does on MCP Framework Personal

AI agents invoke snyk_test_severity_filter to trigger actions in MCP Framework Personal. 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.

RISK

Why snyk_test_severity_filter is rated High

The tool executes an external security scanning process (snyk test) filtered by severity level. This falls under Execute because it triggers an external operation (Snyk CLI/API scan). The blast radius is high because it runs against potentially sensitive codebases and could reveal security vulnerabilities or interact with external services, though it is primarily a read/scan operation wrapped in an execution context.

From the tool's definition 'Ejecuta snyk test' — explicitly runs (executes) a Snyk security test, which is an external tool invocation that scans code/dependencies for vulnerabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snyk_test_severity_filter safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snyk_test_severity_filter, this is the rule to start with:

snyk_test_severity_filter Rate-limited

snyk_test_severity_filter 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snyk_test_severity_filter": {
      "limits": [
        {
          "counter": "snyk_test_severity_filter_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every snyk_test_severity_filter call is checked against it from then on.

FAQ

Questions about snyk_test_severity_filter

What does the snyk_test_severity_filter tool do? +

Ejecuta snyk test filtrando por severidad. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on snyk_test_severity_filter? +

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

What risk level is snyk_test_severity_filter? +

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

Can I rate-limit snyk_test_severity_filter? +

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

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

snyk_test_severity_filter is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 811 MCP Framework Personal tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →