Low Risk

get_event_info

获取活动信息(暂未实现,返回占位符)

How to control get_event_info ↓

What get_event_info does on Doctah-MCP

AI agents call get_event_info to retrieve information from Doctah-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_event_info needs a policy

This tool retrieves/queries event information from the Arknights game database with no capability to modify, delete, or execute external operations. Even though the feature is not yet implemented and returns a placeholder, its intended purpose is to read and return data. It aligns with the server's documented function of enabling 'search and access' to game data.

From the tool's definition Tool name is 'get_event_info' which retrieves event information. Description states '获取活动信息(暂未实现,返回占位符)' (Get event information - not yet implemented, returns placeholder).

Documented attack patterns abuse exactly the kind of access get_event_info gives an agent:

How to control get_event_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Doctah-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_event_info:

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

get_event_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Doctah-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_event_info

What does the get_event_info tool do? +

获取活动信息(暂未实现,返回占位符). It is categorised as a Read tool in the Doctah-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_event_info? +

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

What risk level is get_event_info? +

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

Can I rate-limit get_event_info? +

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

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

get_event_info is provided by the Doctah- MCP server (tonybotni/doctah-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Doctah-MCP tool call.

Start from Doctah-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Doctah-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.