AI agents call list_posts to retrieve information from Portfolio 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 blog post data without modifying, deleting, or executing anything. It is a straightforward read operation with minimal risk—the worst outcome would be information disclosure of already-public portfolio content. Severity is low due to limited blast radius and no irreversible consequences.
From the tool's definition Tool name 'list_posts' and description 'List all blog posts with their frontmatter' indicate a retrieval operation with no side effects. The verb 'list' is explicitly listed in the Read category examples.
Attacks that exploit this kind of access
List all blog posts with their frontmatter. It is categorised as a Read tool in the Portfolio MCP Server, which means it retrieves data without modifying state.
Register the Portfolio 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 Portfolio. 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 Portfolio MCP server (sohumsuthar/portfolio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_posts is one line of Portfolio's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →