Get detailed information about Srikanth
AI agents call get_tech_stack 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 only retrieves existing portfolio data without any ability to modify, delete, or execute operations. It fits the Read category as a simple data retrieval operation. The severity is low because disclosing technical skills information poses minimal risk—it is typically public-facing portfolio content. Confidence is high based on the clear retrieval-only nature of the operation.
From the tool's definition Tool is named 'get_tech_stack' and described as retrieving information about Srikanth's tech stack. The server description states it 'retrieves or queries data' including 'skills'.
Attacks that exploit this kind of access
Get detailed information about 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 get_tech_stack: 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_tech_stack 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_tech_stack 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_tech_stack. 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_tech_stack 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 →