List scheduled/published posts with filtering by status, platform, date range
AI agents call list_posts to retrieve information from Publora MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing posts with optional filtering parameters. It performs no writes, deletes, or execution of external operations—purely a read operation that returns information without side effects. Low severity because access to post metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_posts' and description 'List scheduled/published posts with filtering by status, platform, date range' indicate data retrieval with no modification or deletion of resources.
Attacks that exploit this kind of access
List scheduled/published posts with filtering by status, platform, date range. It is categorised as a Read tool in the Publora MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Publora MCP Server MCP server in PolicyLayer and add a rule for 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 Publora MCP Server. Nothing to install.
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 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 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.
list_posts is provided by the Publora MCP Server MCP server (publora/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →