Obsidian記事をnoteに公開（エディタUI操作で書式を適用、画像を自動挿入）
AI agents use publish-from-obsidian to create or update resources in Note Com MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Note Com MCP Server environment.
An AI agent can call publish-from-obsidian faster than any human can review — one bad instruction and it creates or modifies resources in Note Com MCP Server by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access publish-from-obsidian gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Note Com MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for publish-from-obsidian:
{
"version": "1",
"default": "deny",
"tools": {
"publish-from-obsidian": {
"limits": [
{
"counter": "publish-from-obsidian_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}publish-from-obsidian 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.
Obsidian記事をnoteに公開（エディタUI操作で書式を適用、画像を自動挿入）. It is categorised as a Write tool in the Note Com MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Note Com MCP Server MCP server in PolicyLayer and add a rule for publish-from-obsidian: 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 Note Com MCP Server. Nothing to install.
publish-from-obsidian 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 publish-from-obsidian 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 publish-from-obsidian. 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.
publish-from-obsidian is provided by the Note Com MCP Server MCP server (shimayuz/note-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Note Com MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Note Com MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.