Low Risk

get_block_attrs

获取块属性

How to control get_block_attrs ↓

AI agents call get_block_attrs 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 block attributes from SiYuan Note, which is a read-only query operation. It does not create, modify, delete, or execute anything—it only fetches existing data. The low severity reflects minimal blast radius if misused by an AI agent, as reading attributes cannot directly harm data or systems.

From the tool's definition Tool name 'get_block_attrs' and description '获取块属性' (get block attributes) indicate retrieval of metadata about a block without modification. The verb 'get' is characteristic of read operations.

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

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

get_block_attrs 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_block_attrs tool do? +

获取块属性. 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_block_attrs? +

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

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

Can I rate-limit get_block_attrs? +

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

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

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