list_survey_invitations
List survey invitation history without exposing token hashes or old invitation tokens.
This record as markdown: /tools/io-favcrm-favcrm/list-survey-invitations.md
What list_survey_invitations does on FavCRM
AI agents call list_survey_invitations to retrieve information from FavCRM 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 invitations (default 50) |
surveyId | string | Yes | Survey ID |
Parameters from the server's own tool schema.
Why list_survey_invitations is rated Low
This tool retrieves historical data about survey invitations without modifying, executing operations, or destructively altering any records. The security precaution mentioned (not exposing tokens) reinforces that it is a safe read operation. The blast radius of misuse is low—an agent could enumerate invitations to understand business activity, but cannot change state or cause financial harm.
From the tool's definition Tool name contains 'list' and description states it 'List[s] survey invitation history'. The phrase 'without exposing token hashes or old invitation tokens' indicates read-only retrieval with appropriate redaction of sensitive fields.
Attacks that exploit this kind of access
The rule that runs list_survey_invitations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_survey_invitations, this is the rule to start with:
list_survey_invitations 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 FavCRM, apply this rule, and every list_survey_invitations call is checked against it from then on.
Questions about list_survey_invitations
List survey invitation history without exposing token hashes or old invitation tokens. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_survey_invitations accepts 2 parameters: limit, surveyId. Required: surveyId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for list_survey_invitations: 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 FavCRM. Nothing to install.
list_survey_invitations 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_survey_invitations 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_survey_invitations. 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_survey_invitations is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue