Low Risk

search_content

search_content

How to control search_content ↓

AI agents call search_content to retrieve information from Weibo 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 searches or queries content on Weibo without modifying, deleting, or executing arbitrary operations. It has no side effects and simply returns data results. It falls squarely into the Read category with low severity, as misuse would primarily result in unauthorized information disclosure rather than data loss or system compromise.

From the tool's definition Tool name 'search_content' combined with sibling tools like 'search_topics', 'search_users', 'get_feeds', and 'get_profile' all indicate retrieval and querying operations.

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

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

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

search_content 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 Weibo 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 search_content tool do? +

search_content. It is categorised as a Read tool in the Weibo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_content? +

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

What risk level is search_content? +

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

Can I rate-limit search_content? +

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

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

search_content is provided by the Weibo MCP Server MCP server (qinyuanpei/mcp-server-weibo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Weibo MCP Server tool call.

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

Free to start. No card required.

10 Weibo 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.