Low Risk

get_related_links

获取与指定内容相关的链接

How to control get_related_links ↓

What get_related_links does on Micro

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

Low Risk

Why get_related_links needs a policy

This tool retrieves or queries related links based on input content. It performs a read-only operation that fetches information without creating, modifying, deleting, or executing any actions. The function signature suggests link discovery/search functionality, which falls squarely into the Read category with minimal security risk.

From the tool's definition Tool name 'get_related_links' and description '获取与指定内容相关的链接' (get links related to specified content) indicate retrieval of existing data without modification or side effects.

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

How to control get_related_links

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

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

get_related_links 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 Micro — 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.

Related tools and policies

Go deeper

Questions about get_related_links

What does the get_related_links tool do? +

获取与指定内容相关的链接. It is categorised as a Read tool in the Micro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_related_links? +

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

What risk level is get_related_links? +

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

Can I rate-limit get_related_links? +

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

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

get_related_links is provided by the Micro MCP server (jd-opensource/microapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Micro tool call.

Start from Micro, 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.

3 Micro tools catalogued and risk-classified — across an index of 43,000+ 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.