AI agents use create_math_block 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.
The tool creates (adds) a LaTeX math block within an Obsidian vault note, which is a reversible data modification operation. It does not execute code, delete data, move funds, or trigger external processes—it simply appends formatted mathematical content to a note, consistent with other Write-category tools on this server like 'append_to_note' and 'add_tags'.
From the tool's definition Tool name 'create_math_block' and description 'Add LaTeX math block' indicate creation of a new content block within a note. This is a write operation that modifies note content by adding a math block element.
Documented attack patterns abuse exactly the kind of access create_math_block 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 create_math_block:
{
"version": "1",
"default": "deny",
"tools": {
"create_math_block": {
"limits": [
{
"counter": "create_math_block_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_math_block 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.
Add LaTeX math block. 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 create_math_block: 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.
create_math_block 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 create_math_block 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 create_math_block. 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.
create_math_block 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.