AI agents use standardize_formatting to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
This tool modifies note formatting reversibly without deleting content, making it a Write operation. Severity is medium because unintended formatting standardization across multiple notes could degrade readability or break custom formatting conventions, but changes are typically reversible through undo or manual correction. High confidence due to clear description indicating modification of vault content.
From the tool's definition Tool description states 'Fix inconsistent markdown formatting' which modifies note content. The name 'standardize_formatting' and verb 'Fix' indicate the tool alters existing markdown structure within Obsidian vault notes.
Documented attack patterns abuse exactly the kind of access standardize_formatting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for standardize_formatting:
{
"version": "1",
"default": "deny",
"tools": {
"standardize_formatting": {
"limits": [
{
"counter": "standardize_formatting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} standardize_formatting 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.
Fix inconsistent markdown formatting. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for standardize_formatting: 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 Obsidian MCP Server. Nothing to install.
standardize_formatting 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 standardize_formatting 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 standardize_formatting. 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.
standardize_formatting is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, 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.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.