根据ID获取单个简历的详细信息。
AI agents call get_resume_by_id to retrieve information from Resume Filter 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 resume data by ID with no side effects or modifications. It is a straightforward read operation that queries existing data. The severity is low because resume data, while potentially sensitive, is only being retrieved without alteration, deletion, or external action triggered. The confidence is high because the intent is unambiguous from both the naming convention and description.
From the tool's definition Tool name 'get_resume_by_id' and description '根据ID获取单个简历的详细信息' (get detailed information of a single resume by ID) indicate data retrieval without modification. The tool fetches and returns resume content based on an identifier.
Attacks that exploit this kind of access
根据ID获取单个简历的详细信息。. It is categorised as a Read tool in the Resume Filter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Resume Filter MCP Server MCP server in PolicyLayer and add a rule for get_resume_by_id: 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 Resume Filter MCP Server. Nothing to install.
get_resume_by_id 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_resume_by_id 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_resume_by_id. 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_resume_by_id is provided by the Resume Filter MCP Server MCP server (xinmu-wyb/mcp). 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 →