AI agents call get_cv_tailoring_prompt to retrieve information from Medwriter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool provides expert prompts (guidance text) to help format a CV for applicant tracking systems. It does not modify any user data, execute commands, create financial obligations, or trigger external side effects. The function is purely informational/generative—it reads the job posting context and outputs suggestion text. No reversible writes occur; no data is persisted or altered on external systems.
From the tool's definition Tool returns a prompt for CV/resume tailoring guidance; it retrieves or generates templated advice without modifying, deleting, or executing external operations. The description states it tailors content 'for ATS alignment'—a read-oriented guidance function.
Attacks that exploit this kind of access
[PRO] Tailor a CV/resume to a medical writing job posting for ATS alignment. It is categorised as a Read tool in the Medwriter MCP Server, which means it retrieves data without modifying state.
Register the Medwriter MCP server in PolicyLayer and add a rule for get_cv_tailoring_prompt: 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 Medwriter. Nothing to install.
get_cv_tailoring_prompt 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_cv_tailoring_prompt 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_cv_tailoring_prompt. 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_cv_tailoring_prompt is provided by the Medwriter MCP server (pubspro/medwriter-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 →