Low Risk

dayi_query_auto

dayi_query_auto

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

AI agents call dayi_query_auto to retrieve information from Dayi 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 dayi_query_auto 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.

dayi.yaml
tools:
  dayi_query_auto:
    rules:
      - action: allow

See the full Dayi policy for all 2 tools.

Tool Name dayi_query_auto
Category Read
MCP Server Dayi MCP Server
Risk Level Low

Agents calling read-class tools like dayi_query_auto 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 dayi_query_auto tool do? +

dayi_query_auto. It is categorised as a Read tool in the Dayi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dayi_query_auto? +

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

What risk level is dayi_query_auto? +

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

Can I rate-limit dayi_query_auto? +

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

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

dayi_query_auto is provided by the Dayi MCP server (@xiaoyibao_2025/dayi-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Dayi

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.