assemble_resume
AI agents use assemble_resume to create or update resources in Nima Career — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nima Career environment.
The tool creates or generates a resume (a new output artifact) by assembling pre-approved career material. This is a Write operation—it produces a new document that combines existing curated data. However, severity is low because: (1) the source data is described as 'public-safe,' (2) the operation is reversible (a resume can be discarded or regenerated), and (3) no external systems are modified.
From the tool's definition Tool name 'assemble_resume' indicates creation/compilation of a document. Description is empty, limiting direct evidence. Sibling tools (list_projects, list_experience, get_profile, etc.) are all read-only retrievals from a public-safe career history.
Attacks that exploit this kind of access
assemble_resume. It is categorised as a Write tool in the Nima Career MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nima Career MCP server in PolicyLayer and add a rule for assemble_resume: 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 Nima Career. Nothing to install.
assemble_resume is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assemble_resume 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 assemble_resume. 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.
assemble_resume is provided by the Nima Career MCP server (nima-karami/nima-career-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 →