compliance_report

THE RISK

Low Risk

Why compliance_report needs a policy

This tool retrieves and queries pre-computed security compliance data from a DeepSource project. It has no side effects, does not execute code, create, modify, or delete data. The read-only nature and informational purpose (reporting) place it firmly in the Read category with low severity, as misuse would only expose or retrieve existing information rather than cause operational harm.

From the tool's definition The tool description explicitly states 'Get security compliance reports' — a retrieval operation with no modification, deletion, or execution capability.

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

POLICY

How to control compliance_report

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 compliance_report:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compliance_report": {}
  }
}

compliance_report is read-only, so it stays allowed — but 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DeepSource MCP Server tools

Write update_metric_setting Update the settings for a quality metric 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 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about compliance_report

What does the compliance_report tool do? +

Get security compliance reports from a DeepSource project. It is categorised as a Read tool in the DeepSource MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compliance_report? +

Register the DeepSource MCP Server MCP server in PolicyLayer and add a rule for compliance_report: 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 compliance_report? +

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

Can I rate-limit compliance_report? +

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

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

compliance_report 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 →