Put a real policy layer in front of local AI tools.

SecureMCP-Lite wraps any local stdio MCP server, enforces a YAML policy, returns proper JSON-RPC denials, and keeps logs readable for humans while stdout stays protocol-clean for agents.

Read the docs Social media kit Check compatibility Go to Repo npm Package

Verified in this reponpm run demo:blockednpm run demo:allowednpm run demo:session

secure-mcp.yml

tools:
  allow:
    - read_file
    - list_dir

  parameterRules:
    read_file:
      path:
        allow:
          - '^/workspace/src(?:/.*)?$'
        deny:
          - '\.\.'

stderr

INFO    SecureMCP-Lite proxy started
ALLOWED Forwarding client request method="tools/call" id=2 tool="read_file"
BLOCKED Tool "delete_file" is not allowlisted by SecureMCP-Lite policy.

Why teams use it

Useful on day one, narrow on purpose.

SecureMCP-Lite is not trying to be a platform. It is a local-first enforcement layer that is small enough to audit and practical enough to adopt without rebuilding your workflow.

Control

Allowlist tools, restrict parameters, block traversal, deny dangerous shell or SQL patterns, and rate-limit repeated calls.

Reliability

Reject malformed JSON-RPC locally, fail closed when the target dies, and keep stdout clean for MCP while logs stay on stderr.

Adoption

Run it with npx, install it into a repo, share one policy file, and wire the same wrapper command into multiple AI clients.

Use cases

Built for developers, maintainers, and security-minded AI users.

Read-only coding assistant

Let AI agents inspect a repo, search files, and explain code without granting silent write or shell access.

Guarded shell assistant

Keep shell access available, but block obvious high-risk commands like rm -rf, curl | sh, or sudo.

Safer SQL workflows

Allow analytics and schema exploration while denying destructive query families such as DROP, TRUNCATE, and ALTER.

Shared team policy

Check one YAML policy into the repo so contributors and reviewers inherit the same MCP guardrails instead of inventing their own local setup.

Compatibility

Best today for local stdio clients.

The current MVP is intentionally stdio-first. That makes it a strong fit for local MCP clients, and not yet a direct fit for remote-only MCP connector surfaces.

strongAI coding agents