mcp-tools

mcp-tools is a cursor rule for Cursor from leancoderkavy/premiere-pro-mcp. It costs 0 tokens per session (257 once invoked), scanned A, original, MIT.

A set of rules for defining and registering MCP tools, which are structured actions that an AI assistant can call. It covers input schemas, permissions, tests, documentation, and reading application state back after a change.

In plain words
What is it for?
It is for adding or changing MCP tool modules, validating inputs, controlling inspect or edit permissions, testing failures and escaping, and reporting whether a mutation was verified.
Why use it?
It prevents the tool list, parameters, authority, tests, and documentation from drifting apart. It also avoids treating a host's response as proof that a change was actually saved.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for adding or changing MCP tool modules, validating inputs, controlling inspect or edit permissions, testing failures and escaping, and reporting whether a mutation was verified.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/leancoderkavy/premiere-pro-mcp/mcp-tools
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.

Clone the repo
git clone --depth 1 https://github.com/leancoderkavy/premiere-pro-mcp

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-tools

README.md
[![agentmods](https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/mcp-tools/github.svg)](https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/mcp-tools)
Your own site
<a href="https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/mcp-tools"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/mcp-tools/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-tools

Your own site · 80×15
<a href="https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/mcp-tools"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/mcp-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 257 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00257
Opus 5.5 $0.00000 $0.00103
Sonnet 5.5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 26d ago against content hash 842e4d037b4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-tools 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 26d ago.

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/mcp-tools.mdc · 21 lines

What it actually says

MCP tools

Each module exports getXTools(...) returning a Record<string, ToolDef> with description, JSON Schema parameters (every property described), and handler. Register new modules in src/server.ts and in tests/tools/tool-modules.test.ts when that catalog lists modules.

  • Keep schemas, descriptions, registrations, structured results, authority, tests, and docs/supported-actions.md synchronized.
  • Default authority is inspect,edit,export,filesystem. Do not enable unsafe-script to paper over a missing operation.
  • Mutating tools must read Premiere state back. Report committed, verified, committed_unverified, or failure. A host return value is not proof of success.
  • Do not silently retry a failed UXP mutation through CEP or QE.
  • Add tests for behavior, failure paths, escaping, validation, and authority. Vitest mocks the bridge; it does not prove a live host.
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. 26d ago First seen · 21 lines · 0 tokens per session scan A 842e4d037b4d

Subscribe to this mod's changes

mcp-tools is a cursor rule published in the GitHub repository leancoderkavy/premiere-pro-mcp (387 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 tokens. 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-09-20.