Low Risk

posts_browse

Browse and list posts with filtering and pagination

Part of the Ghost CMS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call posts_browse to retrieve information from Ghost CMS MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though posts_browse only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

hithereiamaliff-mcp-ghostcms.yaml
tools:
  posts_browse:
    rules:
      - action: allow

See the full Ghost CMS MCP Server policy for all 44 tools.

Tool Name posts_browse
Category Read
Risk Level Low

View all 44 tools →

Agents calling read-class tools like posts_browse have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the posts_browse tool do? +

Browse and list posts with filtering and pagination. It is categorised as a Read tool in the Ghost CMS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on posts_browse? +

Add a rule in your Intercept YAML policy under the tools section for posts_browse. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ghost CMS MCP Server MCP server.

What risk level is posts_browse? +

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

Can I rate-limit posts_browse? +

Yes. Add a rate_limit block to the posts_browse rule in your Intercept 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 posts_browse completely? +

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

posts_browse is provided by the Ghost CMS MCP Server MCP server (hithereiamaliff/mcp-ghostcms). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ghost CMS MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.