AI agents use apply_adapt_framework to create or update resources in Medwriter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medwriter environment.
An AI agent can call apply_adapt_framework faster than any human can review — one bad instruction and it creates or modifies resources in Medwriter by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
[PRO] Apply the ADAPT framework to any base prompt for precision output. It is categorised as a Write tool in the Medwriter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Medwriter MCP server in PolicyLayer and add a rule for apply_adapt_framework: 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.
apply_adapt_framework 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 apply_adapt_framework 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 apply_adapt_framework. 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.
apply_adapt_framework 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 →