# get_speaking

Conference talks and panels. Optionally filter by year (e.g. '2024').

Agent View of the PolicyLayer registry record for `get_speaking`. HTML page: https://policylayer.com/tools/com-frankponcelet-profile/get-speaking

## Facts

- Tool: `get_speaking`
- 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: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `year` | string | no | Four-digit year to filter by, e.g. '2024'. |

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": "get_speaking",
    "arguments": {}
  }
}
```

## Why get_speaking is rated Low

This tool retrieves historical conference and panel information, which is a straightforward data query operation. There is no capability to modify, delete, or execute any actions—only to fetch and optionally filter existing speaking records. This is a classic Read operation with minimal blast radius if misused by an AI agent.

From the tool's own definition: "Tool name is 'get_speaking' with description 'Conference talks and panels.' The server is explicitly marked as 'Read-only' and the tool retrieves speaking engagement information without any side effects or modification capabilities."

## Use case

AI agents call get_speaking 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": {
    "get_speaking": {}
  }
}
```

## 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
- `list_articles` — Read — https://policylayer.com/tools/com-frankponcelet-profile/list-articles.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