sidclaw_evaluateLABSCO SUMMARY
The proxy adds no tools of its own — the six sidclaw_* tools listed here come from its companion server, @sidclaw/mcp-tools.
That is what makes it composable: point it at a database or filesystem server and the agent's experience is unchanged except that the dangerous calls now stop for a decision. Deny-by-default is the setting to plan around — nothing runs until a policy matches it, so the first job after wiring it in is writing the policies for the operations you expect.
What it is
A governance proxy that sits between an agent and an upstream MCP server. It intercepts tool calls, evaluates each one against your policies, and forwards only the allowed ones; tool listing, resources and prompts pass through unchanged.
What you get
- Policy evaluation on every tools/call before it reaches the upstream server, with allow, approval required, or deny as the outcomes
- Per-tool mappings with glob patterns, so db_* or *_query can carry their own operation name, target integration, resource scope and data classification
- skip_governance on named tools, letting read-only calls like schema introspection through without an evaluation round trip
- Two approval behaviours: return an error immediately so the agent can tell the user and retry, or block until a reviewer decides, up to a configurable timeout
- Data classifications of public, internal, confidential and restricted, with a default for anything unmapped
- Outcomes recorded back for the audit trail, whether the call succeeded or failed
- An HTTP mode alongside stdio, exposing an authenticated MCP endpoint and an unauthenticated health check for remote clients
Requirements
An account with the service and an API key. The published server definition takes SIDCLAW_API_KEY and SIDCLAW_AGENT_ID, plus SIDCLAW_UPSTREAM_CMD and SIDCLAW_UPSTREAM_ARGS naming the server it wraps; SIDCLAW_APPROVAL_MODE selects whether an approval returns immediately or waits. Installed from npm as @sidclaw/sdk and run over stdio. Without a matching policy, actions are denied by default.
Setup effort
One command plus a key — npm install @sidclaw/sdk, then supply credentials
USE CASES
01
Letting an agent touch production data
Wrap the database server so writes require approval while reads pass through.
02
Keeping cheap calls cheap
Mark schema introspection tools as skipping evaluation so they do not pay a round trip.
03
Putting a person in the loop
Set the approval mode to block, so a flagged call waits for a reviewer instead of failing.
04
Classifying what the agent reaches
Map each tool to an operation and data classification so the policy engine can reason about it.
05
Answering what an agent did last week
Read the recorded outcomes for every evaluated call, successful or not.
6 tools
Listed in project docs. Your client may show a different list.
sidclaw_recordsidclaw_approvesidclaw_policiessidclaw_session_startsidclaw_session_endBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- SIDCLAW_API_KEY in your environment
- SIDCLAW_AGENT_ID in your environment
- SIDCLAW_UPSTREAM_CMD in your environment
- SIDCLAW_UPSTREAM_ARGS in your environment
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install @sidclaw/sdkMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"postgres-governed": {
"command": "npx",
"args": [
"-y",
"@sidclaw/sdk",
"sidclaw-mcp-proxy",
"--transport",
"stdio"
],
"env": {
"SIDCLAW_API_KEY": "<YOUR_SIDCLAW_API_KEY>",
"SIDCLAW_AGENT_ID": "<YOUR_SIDCLAW_AGENT_ID>",
"SIDCLAW_UPSTREAM_CMD": "npx",
"SIDCLAW_UPSTREAM_ARGS": "-y,@modelcontextprotocol/server-postgres,postgresql://localhost/mydb"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"postgres-governed": {
"command": "npx",
"args": [
"-y",
"@sidclaw/sdk",
"sidclaw-mcp-proxy",
"--transport",
"stdio"
],
"env": {
"SIDCLAW_API_KEY": "<YOUR_SIDCLAW_API_KEY>",
"SIDCLAW_AGENT_ID": "<YOUR_SIDCLAW_AGENT_ID>",
"SIDCLAW_UPSTREAM_CMD": "npx",
"SIDCLAW_UPSTREAM_ARGS": "-y,@modelcontextprotocol/server-postgres,postgresql://localhost/mydb"
}
}
}
}Any MCP client — governance tools (@sidclaw/mcp-tools)
ANY MCP CLIENT — GOVERNANCE TOOLS (@SIDCLAW/MCP-TOOLS) · JSON
{
"mcpServers": {
"sidclaw": {
"command": "npx",
"args": [
"-y",
"@sidclaw/mcp-tools"
],
"env": {
"SIDCLAW_BASE_URL": "https://api.sidclaw.com",
"SIDCLAW_API_KEY": "<YOUR_SIDCLAW_API_KEY>",
"SIDCLAW_AGENT_ID": "claude-code"
}
}
}
}
