Insert a marker into the log buffer. Use to bracket an action: call once before the action, perform the action with other tools, then call again with the SAME id. Afterward, query_logs({ between: <id> }) returns exactly the logs produced between the two markers. If you only call it once, query_lo...
AI agents use log_mark to create or update resources in Tauri Plugin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tauri Plugin environment.
log_mark performs a reversible write operation to a log buffer (inserting a timestamped/indexed marker). It has no side effects beyond log metadata manipulation and cannot delete or corrupt data. It is a utility for organizing subsequent log queries rather than executing arbitrary operations or accessing sensitive data.
From the tool's definition Tool description states 'Insert a marker into the log buffer' — this creates/modifies log state by inserting a marker with a given id.
Documented attack patterns abuse exactly the kind of access log_mark gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tauri Plugin, and nothing reaches the server without passing your rules. This is the rule we recommend for log_mark:
{
"version": "1",
"default": "deny",
"tools": {
"log_mark": {
"limits": [
{
"counter": "log_mark_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}log_mark 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.
Insert a marker into the log buffer. Use to bracket an action: call once before the action, perform the action with other tools, then call again with the SAME id. Afterward, query_logs({ between: <id> }) returns exactly the logs produced between the two markers. If you only call it once, query_logs treats. It is categorised as a Write tool in the Tauri Plugin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tauri Plugin MCP server in PolicyLayer and add a rule for log_mark: 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 Tauri Plugin. Nothing to install.
log_mark 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_mark 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_mark. 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_mark is provided by the Tauri Plugin MCP server (p3gleg/tauri-plugin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Tauri Plugin tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Tauri Plugin tools catalogued and risk-classified — across an index of 42,500+ MCP servers.