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 server.
Free to start. No card required.
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. PolicyLayer 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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"sync_from_claude_config"
]
}See the full Clevername policy for all 67 tools.
These attack patterns abuse exactly the kind of access sync_from_claude_config gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
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.
Register the Clevername MCP server in PolicyLayer and add a rule for sync_from_claude_config: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Clevername. Nothing to install.
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 PolicyLayer 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 PolicyLayer 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 67 Clevername tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.