moltbook_feed

THE RISK

Low Risk

Why moltbook_feed needs a policy

This tool retrieves and queries feed data without side effects. It does not create, modify, delete, or execute any operations. The sorting parameters are filtering options, not modifications to underlying data. This is a straightforward read operation with minimal risk of misuse.

From the tool's definition Tool description states 'Get posts from Moltbook feed' with sorting options (hot/new/top/rising). The verb 'Get' and the absence of any modification, deletion, or execution language indicate a read-only retrieval operation.

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

POLICY

How to control moltbook_feed

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "moltbook_feed": {}
  }
}

moltbook_feed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Moltbook MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Moltbook MCP Server tools

Write moltbook_comment Add a comment to a post. Write moltbook_post_create Create a new post on Moltbook. Write moltbook_vote Upvote or downvote a post. Read moltbook_profile Get agent profile. Omit name for your own profile. Read moltbook_search Search posts, moltys, and submolts. Read moltbook_submolts List all submolts (communities). Read moltbook_post Get a single post by ID, including comments.

All 8 Moltbook MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about moltbook_feed

What does the moltbook_feed tool do? +

Get posts from Moltbook feed. Sort by hot/new/top/rising. It is categorised as a Read tool in the Moltbook MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on moltbook_feed? +

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

What risk level is moltbook_feed? +

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

Can I rate-limit moltbook_feed? +

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

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

moltbook_feed is provided by the Moltbook MCP Server MCP server (koriyoshi2041/moltbook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Moltbook MCP Server tool call.

Start from Moltbook MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →