extract_keywords
AI agents call extract_keywords to retrieve information from KeyNeg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Keyword extraction is a data analysis operation that retrieves or derives information from input text without modifying, executing external operations, or causing side effects. It produces informational output only. Classified as Read with medium-high confidence due to empty tool description, but contextual evidence from server purpose and sibling tools strongly supports this categorization.
From the tool's definition Tool name 'extract_keywords' combined with sibling tools 'analyze_sentiment', 'batch_analyze', 'full_analysis' and 'get_sentiment_labels' that are clearly Read operations. Server description indicates 'keyword extraction' as a feature.
Attacks that exploit this kind of access
extract_keywords. It is categorised as a Read tool in the KeyNeg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KeyNeg MCP Server MCP server in PolicyLayer and add a rule for extract_keywords: 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 KeyNeg MCP Server. Nothing to install.
extract_keywords 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 extract_keywords 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 extract_keywords. 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.
extract_keywords is provided by the KeyNeg MCP Server MCP server (osseni94/keyneg-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 →