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.
git clone --depth 1 https://github.com/piyushptiwari1/mcpkernelWrote 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.
[](https://agentmods.dev/rules/piyushptiwari1/mcpkernel/mcpkernel-security)<a href="https://agentmods.dev/rules/piyushptiwari1/mcpkernel/mcpkernel-security"><img src="https://agentmods.dev/badge/rules/piyushptiwari1/mcpkernel/mcpkernel-security/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.
<a href="https://agentmods.dev/rules/piyushptiwari1/mcpkernel/mcpkernel-security"><img src="https://agentmods.dev/badge/rules/piyushptiwari1/mcpkernel/mcpkernel-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00386 |
| Opus 5.5 | $0.00000 | $0.00154 |
| Sonnet 5.5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
mcpkernel-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 1mo 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.
What it actually says
MCPKernel Security Rules
Tool Call Safety
- Never pass raw user input directly to tool calls without sanitization
- Always validate tool arguments against expected types and ranges
- Block tool calls that access sensitive files (.env, .pem, .key, credentials)
- Sandbox all code execution tools — never run on the host directly
Policy Configuration
- Define YAML policies in
policies/directory - Each rule needs: id, name, action (allow/deny/log), and tool_patterns
- Map rules to OWASP ASI 2026 categories (ASI-01 through ASI-08)
- Use
arg_patternswith regex to match dangerous argument values
Taint Tracking
- Mark all external inputs (user prompts, API responses) as tainted
- Track taint labels: SECRET, PII, USER_INPUT across tool boundaries
- Block tainted data from reaching sensitive sinks (network, file write)
- Use FULL taint mode in production, LIGHT for development
Audit & Compliance
- Enable DEE (Deterministic Execution Envelopes) for audit trails
- Every tool execution should be replayable with cryptographic verification
- Export audit logs in CEF format for SIEM integration
- Verify audit log integrity before compliance reporting
Agent Integration
- Use
mcpkernel serveas a proxy between agent and MCP tool servers - Configure via
mcpkernel.yamlat project root - Test policies with
mcpkernel validate-policy <file> - Scan Python files for taint issues with
mcpkernel scan <file>
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.
- 1mo ago First seen · 38 lines · 0 tokens per session scan A e145c451ff25
mcpkernel-security is a cursor rule published in the GitHub repository piyushptiwari1/mcpkernel (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 386 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.