Low Risk

query_survey_binding

[Deprecated] 查询问卷与用户系统的绑定关系,返回绑定的参与者列表。支持按参与状态(join_status)、日期(day)、周(week)、月(month)筛选,可选择是否强制获取参与次数(force_join_times)。

Part of the Wjx server.

query_survey_binding 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 WJX →

Free to start. No card required.

AI agents call query_survey_binding to retrieve information from Wjx 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 query_survey_binding 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": {
    "query_survey_binding": {}
  }
}

See the full Wjx policy for all 58 tools.

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

ENFORCE ON MY WJX →

View all 58 tools →

These attack patterns abuse exactly the kind of access query_survey_binding 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 query_survey_binding only ever does what you allow.

SECURE WJX →

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

What does the query_survey_binding tool do? +

[Deprecated] 查询问卷与用户系统的绑定关系,返回绑定的参与者列表。支持按参与状态(join_status)、日期(day)、周(week)、月(month)筛选,可选择是否强制获取参与次数(force_join_times)。. It is categorised as a Read tool in the Wjx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_survey_binding? +

Register the Wjx MCP server in PolicyLayer and add a rule for query_survey_binding: 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 Wjx. Nothing to install.

What risk level is query_survey_binding? +

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

Can I rate-limit query_survey_binding? +

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

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

query_survey_binding is provided by the Wjx MCP server (wjx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wjx tool call.

Deterministic rules across all 58 Wjx 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.