Scan your local Claude MCP config files and import registered servers into Clevername. HTTP/SSE servers become proxied MCP connections — once imported you can delete them from Claude's config and route all tool calls through clevername.net instead. Stdio servers have their API keys/tokens extract...
Part of the Clevername MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call sync_from_claude_config to permanently remove or destroy resources in Clevername. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call sync_from_claude_config in a loop, permanently destroying resources in Clevername. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
sync_from_claude_config:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Clevername policy for all 67 tools.
Agents calling destructive-class tools like sync_from_claude_config have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
sync_from_claude_config is one of the critical-risk operations in Clevername. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Scan your local Claude MCP config files and import registered servers into Clevername. HTTP/SSE servers become proxied MCP connections — once imported you can delete them from Claude's config and route all tool calls through clevername.net instead. Stdio servers have their API keys/tokens extracted from env vars and stored in the encrypted Clevername key vault; if the server has a marketplace equivalent (GitHub, Supabase, Slack, etc.) you can then delete the local entry and activate the marketplace version. Run with dry_run=true first to preview what will be imported.. It is categorised as a Destructive tool in the Clevername MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for sync_from_claude_config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clevername MCP server.
sync_from_claude_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sync_from_claude_config rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for sync_from_claude_config. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
sync_from_claude_config is provided by the Clevername MCP server (@clevername/clevername-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept