update_thinking_profile
AI agents use update_thinking_profile 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.
The tool updates a thinking profile, which is a Write action—it modifies stored user configuration or cognitive preferences without deletion. Severity is medium because profile updates could affect system behavior or decision-making downstream, but the blast radius is limited to the user's own local profile data (per the 'local-first' design).
From the tool's definition Tool name 'update_thinking_profile' indicates modification of user profile data; context from sibling tools (add_memory_entry, add_journal_entry, add_user_topic) confirms this server manages personal user data.
Attacks that exploit this kind of access
update_thinking_profile. 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 update_thinking_profile: 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.
update_thinking_profile 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 update_thinking_profile 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 update_thinking_profile. 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.
update_thinking_profile 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 →