aggregate_reflexions
AI agents call aggregate_reflexions to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description reducing confidence, aggregation is fundamentally a read operation—it retrieves and synthesizes existing data without side effects. In the context of a research companion like Metis that manages user PDFs and knowledge, aggregating reflections would collect stored reflection entries. No destructive, financial, or code-execution capability is implied by the name alone.
From the tool's definition Tool name 'aggregate_reflexions' suggests collecting or summarizing reflective data without modification. The description is empty, limiting direct evidence, but the verb 'aggregate' typically indicates a read/collection operation rather than modification or…
Attacks that exploit this kind of access
aggregate_reflexions. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for aggregate_reflexions: 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.
aggregate_reflexions 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 aggregate_reflexions 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 aggregate_reflexions. 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.
aggregate_reflexions 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 →