entity_extract
Rule-based entity and value extraction with normalised values: dates (ISO, numeric with dmy/mdy, month names, relative "next Friday" / "in 3 days" resolved against a reference date), times with time zones, money (symbols, ISO codes, crypto tickers, k/m/bn scales), percentages and basis points, qu...
This record as markdown: /tools/com-it-scorptech-x402/entity-extract.md
What entity_extract does on ScorpTech x402 API
AI agents call entity_extract to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to scan |
types | array | — | Only these entity types (default all) |
dateOrder | string | — | How to read ambiguous numeric dates like 03/04/2026 |
referenceDate | string | — | Anchor for relative dates and missing years (default today, UTC) |
Parameters from the server's own tool schema.
Why entity_extract is rated Low
Even though entity_extract only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs entity_extract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For entity_extract, this is the rule to start with:
entity_extract is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every entity_extract call is checked against it from then on.
Questions about entity_extract
Rule-based entity and value extraction with normalised values: dates (ISO, numeric with dmy/mdy, month names, relative "next Friday" / "in 3 days" resolved against a reference date), times with time zones, money (symbols, ISO codes, crypto tickers, k/m/bn scales), percentages and basis points, quantities with units, durations in seconds, URLs, emails, hashtags, @mentions, $cashtags, organisations (legal suffixes) and titled persons. Code-point offsets, overlap resolution, type filter. Offline, deterministic, English. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/entity-extract. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
entity_extract accepts 4 parameters: text, types, dateOrder, referenceDate. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for entity_extract: 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 ScorpTech x402 API. Nothing to install.
entity_extract 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 entity_extract 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 entity_extract. 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.
entity_extract is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue