contact_depscope

SERVERDepscope SOURCEcuttalo/depscope-mcp

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-depscope-mcp/contact-depscope.md

WHAT IT DOES

What contact_depscope does on Depscope

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

Parameter	Type	Required	Description
`body`	string	—	Message body (10-8000 chars). Be specific: include package name, ecosystem, error trace, repro steps when applicable.
`kind`	string	—	Ticket category. `anomaly` routes to structured anomaly triage (requires tool_called/observed/expected).
`name`	string	—	Sender display name (optional).
`email`	string	—	Reply-to email of the requester (required for bug/listing/security/partnership).
`company`	string	—	Company / organization (optional).
`package`	string	—	For kind=anomaly: package name involved, if any.
`subject`	string	—	Short subject line (3-200 chars).
`version`	string	—	For kind=anomaly: package version involved, if any.
`expected`	string	—	For kind=anomaly: what you expected to see (1-1500 chars). Be concrete.
`observed`	string	—	For kind=anomaly: what DepScope returned (1-1500 chars).
`ecosystem`	string	—	For kind=anomaly: ecosystem of the involved package, if any.
`tool_called`	string	—	For kind=anomaly: DepScope tool that produced the anomaly (e.g. check_package, get_migration_path).

Parameters from the server's own tool schema.

RISK

Why contact_depscope is rated Medium

This tool creates a support/reporting ticket (bug, listing, security disclosure, anomaly, or partnership request) and returns a ticket or anomaly ID. It creates a new record reversibly (a ticket can be voided/closed), making it a Write operation. Blast radius is low since it only submits an inbound report to DepScope staff and does not modify any package data or execute code.

From the tool's definition Inbound ticket: bug/listing/security/anomaly/partnership... RETURNS: {ticket_id} or {anomaly_id}

Risk signalsAccepts raw HTML/template content (body) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contact_depscope safely

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

contact_depscope Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about contact_depscope

What does the contact_depscope tool do? +

Inbound ticket: bug/listing/security/anomaly/partnership. USE WHEN: reporting wrong data (bug), requesting a new pkg/ecosystem index (listing), disclosing a DepScope security issue (security), flagging a concrete mismatch in another tool's output vs. authoritative source (anomaly — provide tool_called+observed+expected), or partnership/press (partnership). RETURNS: {ticket_id} or {anomaly_id}. It is categorised as a Write tool in the Depscope MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does contact_depscope accept? +

contact_depscope accepts 12 parameters: body, kind, name, email, company, package, subject, version, expected, observed, ecosystem, tool_called. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on contact_depscope? +

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

What risk level is contact_depscope? +

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

Can I rate-limit contact_depscope? +

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

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

contact_depscope is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Depscope, and thousands of servers like it.

This server

All 22 Depscope tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →