Update the threshold for a specific quality metric
AI agents use update_metric_threshold to create or update resources in DeepSource MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DeepSource MCP Server environment.
This tool modifies metric thresholds, which are configuration settings within DeepSource. While this changes system behavior and could affect code quality assessments, it is reversible (thresholds can be adjusted back) and does not delete data or execute arbitrary code. It falls under Write category.
From the tool's definition Tool name 'update_metric_threshold' and description 'Update the threshold for a specific quality metric' indicate modification of configuration settings. The action 'update' is reversible.
Documented attack patterns abuse exactly the kind of access update_metric_threshold gives an agent:
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_threshold:
{
"version": "1",
"default": "deny",
"tools": {
"update_metric_threshold": {
"limits": [
{
"counter": "update_metric_threshold_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_metric_threshold 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.
Free to start. No card required.
Update the threshold for a specific 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.
Register the DeepSource MCP Server MCP server in PolicyLayer and add a rule for update_metric_threshold: 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.
update_metric_threshold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_metric_threshold 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.
Set action: deny in the PolicyLayer policy for update_metric_threshold. 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.
update_metric_threshold 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.
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.
Free to start. No card required.
11 DeepSource MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.