# 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.

Agent View of the PolicyLayer registry record for `list_articles`. HTML page: https://policylayer.com/tools/com-frankponcelet-profile/list-articles

## Facts

- Tool: `list_articles`
- Server: Profile (`https://frankponcelet.com/api/mcp`) — https://policylayer.com/tools/com-frankponcelet-profile.md
- Homepage: https://github.com/FrankNFT-labs/Portifolio
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tag` | string | no | Case-insensitive tag filter for the list, e.g. 'ai-agents'. |
| `slug` | string | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_articles",
    "arguments": {}
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Profile:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_articles": {}
  }
}
```

## Other tools on Profile (8)

- `get_career` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-career.md
- `get_current_focus` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-current-focus.md
- `get_engagement` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-engagement.md
- `get_expertise` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-expertise.md
- `get_persona` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-persona.md
- `get_profile` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-profile.md
- `get_projects` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-projects.md
- `get_speaking` — Read — https://policylayer.com/tools/com-frankponcelet-profile/get-speaking.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-frankponcelet-profile · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-frankponcelet-profile