Low Risk

get_path_by_id

根据 ID 获取存储路径

How to control get_path_by_id ↓

AI agents call get_path_by_id to retrieve information from SiYuan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or queries file path information based on a given ID. It performs a lookup operation without modifying, creating, deleting, or executing anything. The blast radius of misuse is minimal—an attacker could only discover where files are stored, not access, modify, or delete them. This is clearly a Read category tool with low severity.

From the tool's definition Tool name 'get_path_by_id' and description '根据 ID 获取存储路径' (Get storage path by ID) indicates a retrieval operation. The verb 'get' and the function of looking up a path based on an identifier are characteristic of read-only queries with no side effects.

Documented attack patterns abuse exactly the kind of access get_path_by_id 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 get_path_by_id:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_path_by_id": {}
  }
}

get_path_by_id is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_path_by_id tool do? +

根据 ID 获取存储路径. It is categorised as a Read tool in the SiYuan MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_path_by_id? +

Register the SiYuan MCP Server MCP server in PolicyLayer and add a rule for get_path_by_id: 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 get_path_by_id? +

get_path_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_path_by_id? +

Yes. Add a rate_limit block to the get_path_by_id 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 get_path_by_id completely? +

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

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