AI agents call get_manuscript_edit_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 retrieves a prompt template for medical manuscript editing guidance. It reads and returns instructional content without modifying, deleting, or executing operations on external systems or data. The 'get_' prefix and sibling tools (all get_* retrievers) confirm this is a Read operation that supplies prompts/information to the user. No side effects, data modification, or external execution occurs.
From the tool's definition Tool name is 'get_manuscript_edit_prompt' — a getter that retrieves a prompt template. Description states it provides a 'Comprehensive medical manuscript edit prompt', indicating it returns static content/guidance for editing, not execution of edits or…
Attacks that exploit this kind of access
[PRO] Comprehensive medical manuscript edit prompt. 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_manuscript_edit_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_manuscript_edit_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_manuscript_edit_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_manuscript_edit_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_manuscript_edit_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 →