List posts in your Slab workspace, optionally filtered by topic
AI agents call slab__list_posts to retrieve information from Slabby without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing documentation posts from a Slab knowledge base. It performs data retrieval with optional filtering but does not create, modify, delete, or execute operations. The action is read-only with no side effects, fitting the Read category. Severity is low because listing posts has minimal blast radius—an agent cannot cause harm by retrieving documentation metadata.
From the tool's definition Tool name 'list_posts' and description 'List posts in your Slab workspace, optionally filtered by topic' indicate a retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access slab__list_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slabby, and nothing reaches the server without passing your rules. This is the rule we recommend for slab__list_posts:
{
"version": "1",
"default": "deny",
"tools": {
"slab__list_posts": {}
}
}slab__list_posts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List posts in your Slab workspace, optionally filtered by topic. It is categorised as a Read tool in the Slabby MCP Server, which means it retrieves data without modifying state.
Register the Slabby MCP server in PolicyLayer and add a rule for slab__list_posts: 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 Slabby. Nothing to install.
slab__list_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the slab__list_posts 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.
Set action: deny in the PolicyLayer policy for slab__list_posts. 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.
slab__list_posts is provided by the Slabby MCP server (russwyte/slabby). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Slabby, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Slabby tools catalogued and risk-classified — across an index of 43,000+ MCP servers.