write_reflexion
AI agents use write_reflexion to create or update resources in Metis Public Health — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.
This tool creates or modifies reflexion entries (likely user thoughts, reflections, or notes) within the Metis system. It aligns with the Write category as it reversibly creates or updates data. Severity is medium because reflexions appear to be user-generated content without destructive capability, but could impact data integrity if misused by an agent.
From the tool's definition Tool name 'write_reflexion' indicates a write operation (create/modify reflexion data). The empty description limits certainty, but 'write_' prefix clearly signals data modification rather than retrieval or deletion.
Attacks that exploit this kind of access
write_reflexion. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for write_reflexion: 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 Metis Public Health. Nothing to install.
write_reflexion 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 write_reflexion 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 write_reflexion. 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.
write_reflexion is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →