Low Risk

getWallet

Get your Stellar wallet address

How to control getWallet ↓

What getWallet does on Remote Mcp Authless

AI agents call getWallet to retrieve information from Remote Mcp Authless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getWallet needs a policy

This tool retrieves a wallet address from storage—a read-only operation with no side effects. While the server lacks authentication (creating a risk context), the tool itself performs only data retrieval. Severity is low because exposure of a wallet address alone does not enable financial transactions or destructive actions without additional tools (like those that might send funds).

From the tool's definition Tool name 'getWallet' and description 'Get your Stellar wallet address' indicate a retrieval operation with no modification or execution of code/commands.

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

How to control getWallet

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 getWallet:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getWallet": {}
  }
}

getWallet is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Remote Mcp Authless — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getWallet

What does the getWallet tool do? +

Get your Stellar wallet address. It is categorised as a Read tool in the Remote Mcp Authless MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getWallet? +

Register the Remote Mcp Authless MCP server in PolicyLayer and add a rule for getWallet: 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.

What risk level is getWallet? +

getWallet is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getWallet? +

Yes. Add a rate_limit block to the getWallet 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 getWallet completely? +

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

getWallet 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.

Enforce policy on every Remote Mcp Authless tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.