AI agents use log to create or update resources in MCP Notes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Notes environment.
This tool creates or updates data in a reversible manner (typical of log entries in a note-taking system), which falls under the Write category. The severity is low because log entries in a personal notes system have minimal blast radius — the data can be edited or deleted, and there are no destructive, financial, or code execution implications.
From the tool's definition Tool description states 'Create or update today' — indicates creating or modifying data (write operation). The incomplete description suggests it creates or updates a log entry for the current day.
Documented attack patterns abuse exactly the kind of access log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Notes, and nothing reaches the server without passing your rules. This is the rule we recommend for log:
{
"version": "1",
"default": "deny",
"tools": {
"log": {
"limits": [
{
"counter": "log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}log 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.
Free to start. No card required.
Create or update today. It is categorised as a Write tool in the MCP Notes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Notes MCP server in PolicyLayer and add a rule for log: 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 Notes. Nothing to install.
log 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 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. 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 is provided by the MCP Notes MCP server (markacianfrani/mcp-notes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Notes, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP Notes tools catalogued and risk-classified — across an index of 43,000+ MCP servers.