get_survey

Get survey detail, including blocks, publishing status, visibility, settings, and response count.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/get-survey.md

WHAT IT DOES

What get_survey does on FavCRM

AI agents call get_survey 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
`surveyId`	string	Yes	Survey ID

Parameters from the server's own tool schema.

RISK

Why get_survey is rated Low

This tool retrieves survey metadata and configuration without modifying state or triggering side effects. It is a straightforward read operation with minimal risk even if misused by an agent, as it only exposes existing survey information accessible to authenticated users.

From the tool's definition Tool name 'get_survey' and description 'Get survey detail' indicate data retrieval only. The description lists only read operations: 'including blocks, publishing status, visibility, settings, and response count' — all informational queries with no…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_survey 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 get_survey, this is the rule to start with:

get_survey Allowed

get_survey is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_survey": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every get_survey call is checked against it from then on.

FAQ

Questions about get_survey

What does the get_survey tool do? +

Get survey detail, including blocks, publishing status, visibility, settings, and response count. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.

What parameters does get_survey accept? +

get_survey accepts 1 parameter: surveyId. Required: surveyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_survey? +

Register the FavCRM MCP server in PolicyLayer and add a rule for get_survey: 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.

What risk level is get_survey? +

get_survey is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_survey? +

Yes. Add a rate_limit block to the get_survey 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.

How do I block get_survey completely? +

Set action: deny in the PolicyLayer policy for get_survey. 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.

What MCP server provides get_survey? +

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

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →