security

A set of security rules for handling secrets, permissions, network requests, dependencies, and logs in an MCP server.

In plain words
What is it for?
Use it when adding authentication, database operations, logging, HTTP calls, capability checks, or dependency updates.
Why use it?
It reduces the chance of exposing credentials, allowing unintended writes, or leaving requests and processes running without limits.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/evtapps/ditto-mcp/security
Clone the repo
git clone --depth 1 https://github.com/evtapps/ditto-mcp

Made for: Cursor.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00143
Opus 5 $0.00005 $0.00072
Sonnet 5 $0.00002 $0.00029
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash b9cc3b20d31e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/security.mdc · 12 lines

What it actually says

Security Practices

  • Secrets: only via environment variables; avoid CLI args for secrets.
  • Redaction: all logs must pass through the redacting logger; never concatenate secrets into strings that bypass logging APIs.
  • Capability gating: default to read-only (SELECT). Allow writes only when explicitly configured.
  • Policy allow-list: prefer enabling only the exact classes of DQL you need.
  • Timeouts: enforce sane HTTP timeouts; abort hanging requests.
  • Never include access tokens or Ditto keys in error messages, resource content, or tool outputs.
  • Keep dependencies minimal and up-to-date; Dependabot covers npm/actions/docker.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 12 lines · 11 tokens per session scan A b9cc3b20d31e

Subscribe to this mod's changes

security is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 143 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.