获取 Everything 工具信息。
AI agents call get_everything_info to retrieve information from Everything Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about the Everything search engine tool without modifying, executing operations, or deleting data. It is a simple informational query with no side effects, fitting the Read category. Severity is low as it only exposes tool metadata without access to sensitive file contents or system operations.
From the tool's definition Tool name 'get_everything_info' and description '获取 Everything 工具信息' (Get Everything tool information) indicate retrieval of metadata/information about the search tool itself.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
获取 Everything 工具信息。. It is categorised as a Read tool in the Everything Search MCP Server, which means it retrieves data without modifying state.
Register the Everything Search MCP server in PolicyLayer and add a rule for get_everything_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 Everything Search. Nothing to install.
get_everything_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_everything_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.
Set action: deny in the PolicyLayer policy for get_everything_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.
get_everything_info is provided by the Everything Search MCP server (miloira/everything-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →