Get all available categories in the portfolio data
AI agents call get_portfolio_categories to retrieve information from Portfolio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves categorical metadata from portfolio data without side effects. It is a simple query operation that returns information about available data structure rather than performing any write, execute, or destructive operations. The low severity reflects minimal blast radius - misuse would only expose metadata about portfolio organization structure.
From the tool's definition Tool description states 'Get all available categories in the portfolio data' - a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get all available categories in the portfolio data. It is categorised as a Read tool in the Portfolio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Portfolio MCP Server MCP server in PolicyLayer and add a rule for get_portfolio_categories: 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 Portfolio MCP Server. Nothing to install.
get_portfolio_categories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_portfolio_categories 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 get_portfolio_categories. 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.
get_portfolio_categories is provided by the Portfolio MCP Server MCP server (srikanth-karthi/mcp-portfolio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →