1ly_vault_status

Check the status of the wallet/vault provider. Returns provider type, connection state (connected/offline/locked), and wallet addresses.

SERVER1ly SOURCE@1ly/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-vault-status.md

WHAT IT DOES

What 1ly_vault_status does on 1ly

AI agents call 1ly_vault_status to retrieve information from 1ly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why 1ly_vault_status is rated Low

This tool retrieves wallet/vault status information without executing commands, modifying state, or initiating transactions. It is a diagnostic read operation with minimal security impact even if misused by an AI agent.

From the tool's definition Tool description states it 'Check[s] the status' and 'Returns provider type, connection state, and wallet addresses' — purely informational queries with no modification, deletion, execution, or financial transaction.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 1ly_vault_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1ly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 1ly_vault_status, this is the rule to start with:

1ly_vault_status Allowed

1ly_vault_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "1ly_vault_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_vault_status call is checked against it from then on.

FAQ

Questions about 1ly_vault_status

What does the 1ly_vault_status tool do? +

Check the status of the wallet/vault provider. Returns provider type, connection state (connected/offline/locked), and wallet addresses. It is categorised as a Read tool in the 1ly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on 1ly_vault_status? +

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

What risk level is 1ly_vault_status? +

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

Can I rate-limit 1ly_vault_status? +

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

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

1ly_vault_status is provided by the 1ly MCP server (@1ly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1ly, and thousands of servers like it.

This server

All 24 1ly tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →