resolve_post_slug

THE RISK

Low Risk

Why resolve_post_slug needs a policy

This tool only retrieves/converts a post slug to an ID and fetches post details. It is a pure read/lookup operation with no side effects.

From the tool's definition Convert a post slug to post ID and get post details

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

POLICY

How to control resolve_post_slug

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

policy.json

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

resolve_post_slug 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 Featurebase 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 Featurebase MCP Server tools

Destructive delete_comment Delete a comment (soft delete if has replies) Destructive delete_post Delete a post permanently Write add_upvoter Add an upvoter to a post Write create_comment Create a new comment or reply Write create_post Create a new post Write update_comment Update an existing comment Write update_post Update an existing post Read get_comments Get comments for a post or changelog. Available fields: ${commentModel}, replies(${comment

All 12 Featurebase 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 resolve_post_slug

What does the resolve_post_slug tool do? +

Convert a post slug to post ID and get post details. It is categorised as a Read tool in the Featurebase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resolve_post_slug? +

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

What risk level is resolve_post_slug? +

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

Can I rate-limit resolve_post_slug? +

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

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

resolve_post_slug is provided by the Featurebase MCP Server MCP server (marcinwyszynski/featurebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Featurebase MCP Server tool call.

Start from Featurebase 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 →