Low Risk

share_survey

Get the public share link for an existing survey to distribute to respondents. Use when the user is ready to collect responses and says 'share it' (or similar). Requires the project_token.

Part of the Create Survey server.

share_survey is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CREATE SURVEY →

Free to start. No card required.

AI agents call share_survey to retrieve information from Create Survey without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though share_survey only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "share_survey": {}
  }
}

See the full Create Survey policy for all 5 tools.

Get this rule live on your own Create Survey server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CREATE SURVEY →

These attack patterns abuse exactly the kind of access share_survey gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so share_survey only ever does what you allow.

SECURE CREATE SURVEY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the share_survey tool do? +

Get the public share link for an existing survey to distribute to respondents. Use when the user is ready to collect responses and says 'share it' (or similar). Requires the project_token.. It is categorised as a Read tool in the Create Survey MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on share_survey? +

Register the Create Survey MCP server in PolicyLayer and add a rule for share_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 Create Survey. Nothing to install.

What risk level is share_survey? +

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

Can I rate-limit share_survey? +

Yes. Add a rate_limit block to the share_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 share_survey completely? +

Set action: deny in the PolicyLayer policy for share_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 share_survey? +

share_survey is provided by the Create Survey MCP server (https://mcp.feedbk.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Create Survey tool call.

Deterministic rules across all 5 Create Survey tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.