keyword_extract
Keyphrase extraction for tagging, SEO and RAG metadata: RAKE (rapid automatic keyword extraction: candidate phrases split at stopwords/punctuation, scored by word degree / frequency) or TextRank (co-occurrence graph + PageRank, adjacent top words merged into phrases). Returns ranked multi-word ph...
This record as markdown: /tools/com-it-scorptech-x402/keyword-extract.md
What keyword_extract does on ScorpTech x402 API
AI agents call keyword_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 |
|---|---|---|---|
top | integer | — | Number of phrases |
text | string | Yes | Text to analyse |
method | string | — | rake (phrase-oriented) or textrank (graph-based) |
maxWords | integer | — | Longest phrase in words |
minCount | integer | — | Drop phrases seen fewer times |
stopwords | array | — | Extra stopwords (lowercase) |
Parameters from the server's own tool schema.
Why keyword_extract is rated Low
Even though keyword_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 keyword_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 keyword_extract, this is the rule to start with:
keyword_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 keyword_extract call is checked against it from then on.
Questions about keyword_extract
Keyphrase extraction for tagging, SEO and RAG metadata: RAKE (rapid automatic keyword extraction: candidate phrases split at stopwords/punctuation, scored by word degree / frequency) or TextRank (co-occurrence graph + PageRank, adjacent top words merged into phrases). Returns ranked multi-word phrases with score, relative relevance, occurrence count and first offset. Offline, deterministic, English stopword list (add your own); 200 KB input. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/keyword-extract. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
keyword_extract accepts 6 parameters: top, text, method, maxWords, minCount, stopwords. 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 keyword_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.
keyword_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 keyword_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 keyword_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.
keyword_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