Low Risk

get_feeds

get_feeds

How to control get_feeds ↓

AI agents call get_feeds 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 retrieves feed data from Weibo without modifying, deleting, or executing actions. It is a read-only data retrieval operation with no side effects. The 'get_' prefix and context of sibling retrieval tools confirm it performs a query operation. Confidence is slightly reduced due to empty tool description, but the pattern and server purpose strongly indicate a read operation.

From the tool's definition Tool name 'get_feeds' combined with server description indicating it 'retrieve[s] detailed user profiles, timeline content' and 'helps retrieve' data from Weibo.

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

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

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

get_feeds. 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 get_feeds? +

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

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

Can I rate-limit get_feeds? +

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

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

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