Append a message to the log file.
AI agents use agent_state_log_message to create or update resources in Agent State MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent State MCP Server environment.
This tool creates new log entries in an append-only manner. While it writes data, the operation is reversible (log entries can be deleted or cleared separately) and poses minimal risk. There is no data destruction, code execution, financial impact, or irreversible modification of existing records.
From the tool's definition Tool description states it 'Append[s] a message to the log file' - appending is a reversible write operation that creates new log entries without modifying or deleting existing data.
Attacks that exploit this kind of access
Append a message to the log file. It is categorised as a Write tool in the Agent State MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent State MCP Server MCP server in PolicyLayer and add a rule for agent_state_log_message: 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 Agent State MCP Server. Nothing to install.
agent_state_log_message 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 agent_state_log_message 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 agent_state_log_message. 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.
agent_state_log_message is provided by the Agent State MCP Server MCP server (tianhuil/agent-state). 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 →