Read the master resume data pool.
AI agents call get_resume_data to retrieve information from Resume Forge MCP 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 from a pool without executing code, modifying data, deleting data, or committing financial transactions. It is a straightforward data retrieval operation with no side effects. Severity is low because reading resume data poses minimal risk—the data is likely already known to the user or is their own personal information.
From the tool's definition Tool name 'get_resume_data' combined with description 'Read the master resume data pool' explicitly indicates retrieval without modification. The verb 'read' and 'get' are standard indicators of Read category operations.
Attacks that exploit this kind of access
Read the master resume data pool. It is categorised as a Read tool in the Resume Forge MCP MCP Server, which means it retrieves data without modifying state.
Register the Resume Forge MCP server in PolicyLayer and add a rule for get_resume_data: 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 Forge MCP. Nothing to install.
get_resume_data 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_data 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_data. 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_data is provided by the Resume Forge MCP server (jitendrasinghsankhwar/resume-forge-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 →