assemble_brainstorm_context
AI agents call assemble_brainstorm_context 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.
The verb 'assemble' combined with 'brainstorm_context' indicates the tool likely retrieves or organizes information from the user's indexed library or memory systems (evident from sibling tools like add_memory_entry, add_journal_entry). No modification, deletion, execution, or financial operations are implied.
From the tool's definition Tool name 'assemble_brainstorm_context' suggests gathering or compiling existing context/data for brainstorming purposes. The description is empty, limiting direct evidence, but the naming pattern aligns with retrieval/assembly operations.
Attacks that exploit this kind of access
assemble_brainstorm_context. 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 assemble_brainstorm_context: 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.
assemble_brainstorm_context 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 assemble_brainstorm_context 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 assemble_brainstorm_context. 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.
assemble_brainstorm_context 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 →