list_articles
Frank's blog posts. Without arguments, lists all posts (metadata + URLs). Pass slug for one post including its full markdown content, or tag to filter the list. Each post's raw markdown source is also served at <url>.md.
This record as markdown: /tools/com-frankponcelet-profile/list-articles.md
What list_articles does on Profile
AI agents call list_articles to retrieve information from Profile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Case-insensitive tag filter for the list, e.g. 'ai-agents'. |
slug | string | — | Exact post slug (e.g. 'one-file-two-readers') to fetch a single article including its markdown content. |
Parameters from the server's own tool schema.
Why list_articles is rated Low
Even though list_articles only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_articles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Profile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_articles, this is the rule to start with:
list_articles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Profile, apply this rule, and every list_articles call is checked against it from then on.
Questions about list_articles
Frank's blog posts. Without arguments, lists all posts (metadata + URLs). Pass slug for one post including its full markdown content, or tag to filter the list. Each post's raw markdown source is also served at <url>.md. It is categorised as a Read tool in the Profile MCP Server, which means it retrieves data without modifying state.
list_articles accepts 2 parameters: tag, slug. The full parameter table on this page comes from the server's own tool schema.
Register the Profile MCP server in PolicyLayer and add a rule for list_articles: 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 Profile. Nothing to install.
list_articles 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_articles 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_articles. 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_articles is provided by the Profile MCP server (https://frankponcelet.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Profile, and thousands of servers like it.
This server
Across the catalogue