log_agent_run
A write tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/log-agent-run.md
What log_agent_run does on Metis Public Health
AI agents use log_agent_run 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.
Why log_agent_run is rated Medium
The name implies logging or recording information about an agent run, which is a Write operation (creating a log entry). However, the empty description significantly lowers confidence. Based on sibling tools like 'add_journal_entry' and 'add_memory_entry', this server pattern uses 'add_*' for writes, but 'log_*' similarly implies persisting data.
From the tool's definition Tool name 'log_agent_run' suggests writing/recording agent execution data; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs log_agent_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_agent_run, this is the rule to start with:
log_agent_run stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every log_agent_run call is checked against it from then on.
Questions about log_agent_run
log_agent_run is a write tool on the Metis Public Health MCP server. 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 log_agent_run: 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.
log_agent_run 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 log_agent_run 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 log_agent_run. 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.
log_agent_run 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.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue