get_speaking
Conference talks and panels. Optionally filter by year (e.g. '2024').
This record as markdown: /tools/com-frankponcelet-profile/get-speaking.md
What get_speaking does on Profile
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | string | — | Four-digit year to filter by, e.g. '2024'. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_speaking 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 get_speaking, this is the rule to start with:
get_speaking 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 get_speaking call is checked against it from then on.
Questions about get_speaking
Conference talks and panels. Optionally filter by year (e.g. '2024'). It is categorised as a Read tool in the Profile MCP Server, which means it retrieves data without modifying state.
get_speaking accepts 1 parameter: year. 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 get_speaking: 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.
get_speaking 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 get_speaking 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 get_speaking. 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.
get_speaking 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