Remove a contract address from the user
AI agents call removeContractAddress to permanently remove resources in Remote Mcp Authless — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes a contract address association from a user's record. Removal/deletion of data is typically irreversible (Destructive category). The blast radius is medium: losing a contract address mapping could disrupt operations relying on it, and recovery may require manual re-entry. The server has no authentication, increasing misuse risk.
From the tool's definition 'Remove a contract address from the user' — the word 'remove' indicates irreversible deletion of stored data
Documented attack patterns abuse exactly the kind of access removeContractAddress gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Remote Mcp Authless, and nothing reaches the server without passing your rules. This is the rule we recommend for removeContractAddress:
{
"version": "1",
"default": "deny",
"hide": [
"removeContractAddress"
]
}removeContractAddress disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a contract address from the user. It is categorised as a Destructive tool in the Remote Mcp Authless MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Remote Mcp Authless MCP server in PolicyLayer and add a rule for removeContractAddress: 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 Remote Mcp Authless. Nothing to install.
removeContractAddress 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 removeContractAddress 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 removeContractAddress. 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.
removeContractAddress is provided by the Remote Mcp Authless MCP server (kalepail/stellar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Remote Mcp Authless, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Remote Mcp Authless tools catalogued and risk-classified — across an index of 43,000+ MCP servers.