Medium Risk

create_dsn

Create an additional DSN for a project

Risk signalsGenerates new ingest credentials

Part of the Sentry server.

create_dsn can modify Sentry data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SENTRY →

Free to start. No card required.

AI agents use create_dsn to create or modify resources in Sentry. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_dsn repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Sentry.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dsn": {
      "limits": [
        {
          "counter": "create_dsn_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Sentry policy for all 25 tools.

Get this rule live on your own Sentry server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SENTRY →

View all 25 tools →

These attack patterns abuse exactly the kind of access create_dsn gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_dsn only ever does what you allow.

SECURE SENTRY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_dsn tool do? +

Create an additional DSN for a project. It is categorised as a Write tool in the Sentry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dsn? +

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

What risk level is create_dsn? +

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

Can I rate-limit create_dsn? +

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

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

create_dsn is provided by the Sentry MCP server (@getsentry/sentry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sentry tool call.

Deterministic rules across all 25 Sentry tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.