list_executive_partner_meetings
List a partner's Executive Partner Meetings (EPMs). The API route has no pagination; limit/offset are applied client-side by this tool (default cap 200 rows).
This record as markdown: /tools/adrata-starfield-mcp/list-executive-partner-meetings.md
What list_executive_partner_meetings does on Starfield
AI agents call list_executive_partner_meetings to retrieve information from Starfield 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 |
|---|---|---|---|
limit | number | — | Max rows returned (client-side cap, default 200) |
offset | number | — | Rows to skip (client-side) |
partnerId | string | Yes |
Parameters from the server's own tool schema.
Why list_executive_partner_meetings is rated Low
Even though list_executive_partner_meetings 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_executive_partner_meetings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_executive_partner_meetings, this is the rule to start with:
list_executive_partner_meetings 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 Starfield, apply this rule, and every list_executive_partner_meetings call is checked against it from then on.
Questions about list_executive_partner_meetings
List a partner's Executive Partner Meetings (EPMs). The API route has no pagination; limit/offset are applied client-side by this tool (default cap 200 rows). It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
list_executive_partner_meetings accepts 3 parameters: limit, offset, partnerId. Required: partnerId. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for list_executive_partner_meetings: 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 Starfield. Nothing to install.
list_executive_partner_meetings 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_executive_partner_meetings 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_executive_partner_meetings. 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_executive_partner_meetings is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue