menese_portfolio

Get your full portfolio across all 19 supported blockchains (EVM, Solana, Bitcoin, ICP, etc.) plus ICP ecosystem tokens (ckBTC, ckETH, ckUSDC). Requires a configured wallet.

SERVERMcp Menesesdk SOURCEaboodtt404/mcp-menese-sdk

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/aboodtt404-mcp-menese-sdk/menese-portfolio.md

WHAT IT DOES

What menese_portfolio does on Mcp Menesesdk

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

RISK

Why menese_portfolio is rated Low

This tool reads and queries portfolio information across multiple blockchains without creating side effects. However, severity is elevated from low to high because exposing a user's full portfolio across 19 blockchains to an AI agent creates significant privacy and security risks—an agent could infer wallet contents, holdings, and financial position and potentially act on this information if other tools (like…

From the tool's definition Tool description states 'Get your full portfolio' which retrieves portfolio data across blockchains. No modification, deletion, or execution of transactions described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs menese_portfolio safely

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

menese_portfolio Allowed

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

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

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

FAQ

Questions about menese_portfolio

What does the menese_portfolio tool do? +

Get your full portfolio across all 19 supported blockchains (EVM, Solana, Bitcoin, ICP, etc.) plus ICP ecosystem tokens (ckBTC, ckETH, ckUSDC). Requires a configured wallet. It is categorised as a Read tool in the Mcp Menesesdk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on menese_portfolio? +

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

What risk level is menese_portfolio? +

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

Can I rate-limit menese_portfolio? +

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

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

menese_portfolio is provided by the Mcp Menesesdk MCP server (aboodtt404/mcp-menese-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Menesesdk, and thousands of servers like it.

This server

All 11 Mcp Menesesdk tools →

Across the catalogue

The MCP Attack Database →

Guides

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