Getting portfolios
AI agents call get-artifacts-portfolio to retrieve information from HeadHunter API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or retrieves portfolio data from the HeadHunter platform. It performs no modifications, deletions, or external operations. The action is a simple read/fetch operation with minimal security risk if misused by an AI agent—worst case being unauthorized access to existing portfolio information already associated with the authenticated user's account.
From the tool's definition Tool name 'get-artifacts-portfolio' and description 'Getting portfolios' indicate a retrieval operation with no side effects. The 'get-' prefix and verb 'Getting' are standard patterns for read-only data access.
Attacks that exploit this kind of access
Getting portfolios. It is categorised as a Read tool in the HeadHunter API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for get-artifacts-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 HeadHunter API MCP Server. Nothing to install.
get-artifacts-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 get-artifacts-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 get-artifacts-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.
get-artifacts-portfolio is provided by the HeadHunter API MCP Server MCP server (sargonpiraev/hh-mcp-server). 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 →