share_strategy

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 91 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/share-strategy.md

WHAT IT DOES

What share_strategy does on VaultPilot MCP

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

Parameter	Type	Required	Description
`name`	string	Yes	Short human-readable strategy name. e.g. 'stable yield with mild leverage'.
`wallet`	string	—	EVM wallet whose positions feed the strategy structure. At least one of `wallet` / `tronAddress` / `solanaAddress` / `bitcoinAddress` / `litecoinAddress` is req
`authorLabel`	string	—	Optional author handle / label. Omit for an anonymous strategy (no identifier emitted).
`description`	string	—	Optional longer description. Free-form; redaction scan applies.
`riskProfile`	string	—	Self-declared risk profile. Free-form metadata for the recipient — we don't compute or validate it.
`tronAddress`	string	—	TRON mainnet base58 address (T-prefix).
`solanaAddress`	string	—	Solana mainnet base58 pubkey.
`bitcoinAddress`	string	—	Bitcoin mainnet address (any of legacy/p2sh-segwit/bech32/bech32m).
`litecoinAddress`	string	—	Litecoin mainnet address (any of legacy/p2sh/p2sh-segwit/bech32).

Parameters from the server's own tool schema.

RISK

Why share_strategy is rated Low

This tool reads and exports portfolio metadata in anonymized form with no side effects on the user's assets, accounts, or blockchain state. It does not modify data, execute transactions, delete information, or move funds. The anonymization and read-only nature of the export confirm it is a data retrieval operation with minimal risk.

From the tool's definition Tool generates a 'shareable, anonymized JSON snapshot' with 'NO addresses, NO absolute USD values, NO transaction hashes' — it retrieves and formats portfolio structure data (protocol + asset + percentage) for sharing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs share_strategy safely

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

share_strategy Allowed

share_strategy 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": {
    "share_strategy": {}
  }
}

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

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

FAQ

Questions about share_strategy

What does the share_strategy tool do? +

Generate a shareable, anonymized JSON snapshot of the user's portfolio STRUCTURE — protocol + asset + percentage of total — with NO addresses, NO absolute USD values, NO transaction hashes. Use this when the user wants to share their setup ("here's my Solana yield-farming strategy") with another VaultPilot user. Pass at least one of wallet / tronAddress / solanaAddress / bitcoinAddress / litecoinAddress, plus a name and optional description / authorLabel / riskProfile. The recipient pastes the returned jsonString into their own VaultPilot via import_strategy for read-only inspection. v1 emits JSON only; URL hosting is deferred to v2 (depends on hosted-MCP infra). Privacy guard: a regex scan runs on the output before emit and refuses (RedactionError) if any EVM 0x address, TRON T-address, Solana base58 pubkey, 64-hex tx hash, or Solana signature is detected anywhere in the JSON — including in user-supplied free-form fields. Percentages are rounded to 1 decimal to avoid wallet-fingerprint leakage. The strategy describes structure only; recipients cannot replicate amounts or addresses. Read-only — no signing, no broadcast. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does share_strategy accept? +

share_strategy accepts 9 parameters: name, wallet, authorLabel, description, riskProfile, tronAddress, solanaAddress, bitcoinAddress, litecoinAddress. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on share_strategy? +

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

What risk level is share_strategy? +

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

Can I rate-limit share_strategy? +

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

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

share_strategy is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

The MCP Attack Database →

Guides

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