update_metric_setting

THE RISK

Medium Risk

Why update_metric_setting needs a policy

This tool creates or modifies settings reversibly within the DeepSource system. It does not delete data (excluding Destructive), execute arbitrary code (excluding Execute), or move money (excluding Financial).

From the tool's definition Tool name 'update_metric_setting' and description 'Update the settings for a quality metric' indicate modifying configuration data for quality metrics.

Documented attack patterns abuse exactly the kind of access update_metric_setting gives an agent:

POLICY

How to control update_metric_setting

PolicyLayer is an MCP gateway — it sits between your AI agents and DeepSource MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_metric_setting:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_metric_setting": {
      "limits": [
        {
          "counter": "update_metric_setting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_metric_setting stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DeepSource MCP Server tools

Write update_metric_threshold Update the threshold for a specific quality metric Read recent_run_issues Get issues from the most recent analysis run on a specific branch Read run Get a specific analysis run by its runUid or commitOid Read compliance_report Get security compliance reports from a DeepSource project Read dependency_vulnerabilities Get dependency vulnerabilities from a DeepSource project Other example_tool An example tool demonstrating the enhanced plugin format Read project_issues Get issues from a DeepSource project with filtering capabilities Read projects List all available DeepSource projects. Returns a list of project objects with

All 11 DeepSource MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_metric_setting

What does the update_metric_setting tool do? +

Update the settings for a quality metric. It is categorised as a Write tool in the DeepSource MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_metric_setting? +

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

What risk level is update_metric_setting? +

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

Can I rate-limit update_metric_setting? +

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

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

update_metric_setting is provided by the DeepSource MCP Server MCP server (sapientpants/deepsource-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DeepSource MCP Server tool call.

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

CHECK YOUR STACK →