Medium Risk

push_err_msg

推送错误消息

How to control push_err_msg ↓

AI agents use push_err_msg to create or update resources in SiYuan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiYuan MCP Server environment.

Medium Risk

An AI agent can call push_err_msg faster than any human can review — one bad instruction and it creates or modifies resources in SiYuan MCP Server by the hundred, each call as confident as the last.

Documented attack patterns abuse exactly the kind of access push_err_msg gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and SiYuan MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for push_err_msg:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_err_msg": {
      "limits": [
        {
          "counter": "push_err_msg_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

push_err_msg 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.

  1. Create a free account and register SiYuan MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the push_err_msg tool do? +

推送错误消息. It is categorised as a Write tool in the SiYuan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_err_msg? +

Register the SiYuan MCP Server MCP server in PolicyLayer and add a rule for push_err_msg: 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 SiYuan MCP Server. Nothing to install.

What risk level is push_err_msg? +

push_err_msg is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_err_msg? +

Yes. Add a rate_limit block to the push_err_msg 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.

How do I block push_err_msg completely? +

Set action: deny in the PolicyLayer policy for push_err_msg. 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.

What MCP server provides push_err_msg? +

push_err_msg is provided by the SiYuan MCP Server MCP server (xgq18237/siyuan_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SiYuan MCP Server tool call.

Deterministic rules across all 52 SiYuan MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

52 SiYuan MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.