AI agents call test as a supporting operation in DrissionPageMCP workflows.
The tool description says it generates a message requesting text summarization. This appears to be a utility that constructs a prompt/message rather than performing browser automation, data modification, or any destructive/financial action. It does not clearly fit Read, Write, Execute, Destructive, or Financial categories based on the description.
From the tool's definition '生成一个请求对文本进行摘要的用户消息' (Generates a user message requesting text summarization)
Documented attack patterns abuse exactly the kind of access test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for test:
{
"version": "1",
"default": "deny",
"tools": {
"test": {
"limits": [
{
"counter": "test_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}test gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
生成一个请求对文本进行摘要的用户消息。. It is categorised as a Other tool in the DrissionPageMCP MCP Server, which means it performs auxiliary operations.
Register the DrissionPage MCP server in PolicyLayer and add a rule for test: 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 DrissionPageMCP. Nothing to install.
test is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the test 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.
Set action: deny in the PolicyLayer policy for test. 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.
test is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.