AI agents call get_peer_review_response_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.
The tool's purpose is to retrieve and return a pre-existing prompt template to help draft a reviewer response. This is a read-only operation with no side effects, no code execution, no data modification, and no irreversible actions. The severity is low because misuse would at worst produce poorly-worded text with no impact on systems or data.
From the tool's definition Tool name and description indicate it 'Generate[s] a prompt to draft a professional point-by-point reviewer response.' This is a prompt generation tool that retrieves or returns template text for composing a response; it does not modify data, execute external…
Attacks that exploit this kind of access
[FREE] Generate a prompt to draft a professional point-by-point reviewer response. 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_peer_review_response_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_peer_review_response_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_peer_review_response_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_peer_review_response_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_peer_review_response_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 →