AI agents use setWallet 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 tool modifies user data (wallet address) but does not delete it irreversibly or move funds, so it is Write rather than Destructive or Financial. However, the context of a Stellar wallet address in an authentication-less server raises medium severity: incorrect wallet assignment could misdirect transactions, but the action is reversible by calling setWallet again.
From the tool's definition Tool name 'setWallet' and description 'Set your wallet address' indicate modification of user account state. The tool creates or modifies wallet configuration data reversibly.
Documented attack patterns abuse exactly the kind of access setWallet 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 setWallet:
{
"version": "1",
"default": "deny",
"tools": {
"setWallet": {
"limits": [
{
"counter": "setwallet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setWallet 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.
Set your Stellar wallet address. 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 setWallet: 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.
setWallet 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 setWallet 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 setWallet. 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.
setWallet 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.