Search through Srikanth
AI agents call search_portfolio 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 performs search and retrieval operations on portfolio data (experience, skills, contact information). It has no side effects—it only queries and returns information. The sibling tools (get_contact_info, get_portfolio_categories, get_portfolio_item, get_tech_stack) all follow Read patterns.
From the tool's definition Tool name 'search_portfolio' and description context 'Search through Srikanth' combined with server description 'Enables searching and retrieving portfolio data including experience, skills, and contact information through natural language queries.' All verbs…
Attacks that exploit this kind of access
Search through Srikanth. 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 search_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 Portfolio MCP Server. Nothing to install.
search_portfolio 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 search_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.
Set action: deny in the PolicyLayer policy for search_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.
search_portfolio 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 →