Low Risk

query_responses_realtime

实时查询新提交的答卷(队列模式)。查询成功的答卷将从队列移除,无法二次查询。需联系客服开通白名单。

Part of the Wjx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call query_responses_realtime 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_responses_realtime 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.

wjx.yaml
tools:
  query_responses_realtime:
    rules:
      - action: allow

See the full Wjx policy for all 58 tools.

Tool Name query_responses_realtime
Category Read
MCP Server Wjx MCP Server
Risk Level Low

View all 58 tools →

Agents calling read-class tools like query_responses_realtime have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the query_responses_realtime tool do? +

实时查询新提交的答卷(队列模式)。查询成功的答卷将从队列移除,无法二次查询。需联系客服开通白名单。. 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_responses_realtime? +

Add a rule in your Intercept YAML policy under the tools section for query_responses_realtime. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Wjx MCP server.

What risk level is query_responses_realtime? +

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

Can I rate-limit query_responses_realtime? +

Yes. Add a rate_limit block to the query_responses_realtime rule in your Intercept 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_responses_realtime completely? +

Set action: deny in the Intercept policy for query_responses_realtime. 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_responses_realtime? +

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

Enforce policies on Wjx

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.