// MCP TOOL REFERENCE

sint__remove_server

ServerSINT Protocol
CategoryDestructive

WHAT IT DOES

What sint__remove_server does on SINT Protocol

AI agents call sint__remove_server to permanently remove resources in SINT Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why sint__remove_server needs a policy

This operation permanently disables and removes a downstream server integration, causing its tools to become unavailable. While the downstream server may still exist elsewhere, the proxy's configured connection to it is severed in a way that cannot be automatically undone—human intervention or explicit reconfiguration would be required to restore it.

From the tool's definition "Disconnect and remove one downstream MCP server from the running proxy... after removal its aggregated tools disappear from the namespace." The tool irreversibly removes a server and its capabilities from the running system.

Documented attack patterns abuse exactly the kind of access sint__remove_server gives an agent:

POLICY

How to control sint__remove_server

PolicyLayer is an MCP gateway — it sits between your AI agents and SINT Protocol, and nothing reaches the server without passing your rules. This is the rule we recommend for sint__remove_server:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sint__remove_server"
  ]
}

sint__remove_server disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register SINT Protocol — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SINT Protocol tools

Destructive sint__revoke_delegation_tree Cascade-revoke a delegated token and all of its descendants. Use this for incident respons Destructive sint__revoke_token Revoke an active capability token so it can no longer authorize actions. Use this when acc Destructive sint__deny Reject one pending escalated action so it cannot proceed. Use this after review when the r Execute sint__show_hud Show or refresh one HUD panel in the operator interface. Use this to surface approvals, au Execute sint__approve Approve one pending escalated action after human or operator review. Use this only with a Write sint__delegate_to_agent Issue a delegated capability token to a sub-agent with narrower scope than the current tok Write sint__interface_mode Change how the operator interface presents information. Use this when the situation calls Write sint__store_memory Store structured context in the operator memory bank for later retrieval. Use this for dur

All 21 SINT Protocol tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in SINT Protocol → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sint__remove_server

What does the sint__remove_server tool do? +

Disconnect and remove one downstream MCP server from the running proxy. Use this to disable an integration cleanly when it is unhealthy, no longer needed, or should stop exposing tools; after removal its aggregated tools disappear from the namespace. Returns a confirmation message after removal, or an error if the server name is unknown. It is categorised as a Destructive tool in the SINT Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sint__remove_server? +

Register the SINT Protocol MCP server in PolicyLayer and add a rule for sint__remove_server: 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 SINT Protocol. Nothing to install.

What risk level is sint__remove_server? +

sint__remove_server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sint__remove_server? +

Yes. Add a rate_limit block to the sint__remove_server 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.

How do I block sint__remove_server completely? +

Set action: deny in the PolicyLayer policy for sint__remove_server. 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.

What MCP server provides sint__remove_server? +

sint__remove_server is provided by the SINT Protocol MCP server (sint-ai/sint-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SINT Protocol tool call.

Start from SINT Protocol, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

21 SINT Protocol tools catalogued and risk-classified — across an index of 43,000+ MCP servers.