AI agents use setContractAddress to create or update resources in Remote Mcp Authless — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote Mcp Authless environment.
This is a Write operation—it creates or modifies configuration data by adding a contract address to a tracking list. Severity is high because: (1) the server lacks authentication ('authless'), (2) modifying tracked contract addresses could redirect fund flows or compromise monitoring integrity, (3) sibling tools handle sensitive wallet state, and (4) in Web3 contexts, incorrect contract addresses lead to loss of…
From the tool's definition Tool name and description indicate it 'Add[s] a new contract address to track', which creates/modifies data (adding to a tracked list).
Documented attack patterns abuse exactly the kind of access setContractAddress 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 setContractAddress:
{
"version": "1",
"default": "deny",
"tools": {
"setContractAddress": {
"limits": [
{
"counter": "setcontractaddress_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setContractAddress stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a new contract address to track. It is categorised as a Write tool in the Remote Mcp Authless MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote Mcp Authless MCP server in PolicyLayer and add a rule for setContractAddress: 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.
setContractAddress is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setContractAddress 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 setContractAddress. 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.
setContractAddress 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.