ai.entities

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/ai.entities.md

WHAT IT DOES

What ai.entities does on Mcp

AI agents call ai.entities to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ai.entities is rated Low

This is a pure data extraction and analysis tool. It processes input text to identify and classify named entities, returning categorized metadata. There are no side effects, no data modification, no code execution, and no financial operations. The extraction is read-only analysis suitable for indexing and redaction workflows.

From the tool's definition Tool performs 'Named-entity recognition' and 'Extracts people, organizations, locations, dates, money, products, laws, events' for 'knowledge extraction, redaction prep, and document indexing.' It takes text input and returns structured entity data without…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ai.entities safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai.entities, this is the rule to start with:

ai.entities Allowed

ai.entities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ai.entities": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every ai.entities call is checked against it from then on.

FAQ

Questions about ai.entities

What does the ai.entities tool do? +

Named-entity recognition. POST { text }. Extracts people, organizations, locations, dates, money, products, laws, events and more — each with a standard type and mention count. For knowledge extraction, redaction prep, and document indexing. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ai.entities? +

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

What risk level is ai.entities? +

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

Can I rate-limit ai.entities? +

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

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

ai.entities is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →