写入日志到当前工作目录的log目录下,按日期分文件存储
AI agents use logger to create or update resources in MCP Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Toolkit environment.
This tool writes log data to files on the filesystem. It creates or appends to log files organized by date. This is a reversible write operation (files can be deleted or overwritten), so it falls under Write rather than Destructive. Severity is low because logging is a benign side effect with minimal blast radius, though an agent could potentially flood disk space or write sensitive data to logs.
From the tool's definition 写入日志到当前工作目录的log目录下,按日期分文件存储 — 'writes logs' to a log directory, stored by date
Attacks that exploit this kind of access
写入日志到当前工作目录的log目录下,按日期分文件存储. It is categorised as a Write tool in the MCP Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Toolkit MCP server in PolicyLayer and add a rule for logger: 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 MCP Toolkit. Nothing to install.
logger 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 logger 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 logger. 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.
logger is provided by the MCP Toolkit MCP server (zxfgds/mcp-toolkit). 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 →