batch_keyword_difficulty
Score up to 10 keywords in one call. Cost: 10 credits per keyword.
This record as markdown: /tools/com-getappniche-mcp/batch-keyword-difficulty.md
What batch_keyword_difficulty does on Mcp
AI agents call batch_keyword_difficulty 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
store | string | — | Store to score against: 'apple' or 'google'. |
country | string | — | Two-letter ISO country code of the storefront, e.g. 'US', 'DE' (default 'US'). |
keywords | array | Yes | Up to 10 search terms to score in one call, e.g. ['habit tracker', 'daily planner']. |
language | string | — | Language code the keywords are written in, e.g. 'en', 'de' (default 'en'). |
Parameters from the server's own tool schema.
Why batch_keyword_difficulty is rated Low
This is a read-only query tool that retrieves keyword difficulty scores from the App Store & Google Play data. It neither creates, modifies, deletes data, nor executes arbitrary code or financial transactions. The cost in credits is a tracking mechanism, not a financial operation. Classification as Read is appropriate.
From the tool's definition Tool 'batch_keyword_difficulty' scores keywords (ASO keyword analysis) and returns difficulty metrics. The description indicates it 'Score[s] up to 10 keywords' with a credit cost, which is a lookup/analysis operation with no side effects on app data, user…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_keyword_difficulty 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 batch_keyword_difficulty, this is the rule to start with:
batch_keyword_difficulty 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 Mcp, apply this rule, and every batch_keyword_difficulty call is checked against it from then on.
Questions about batch_keyword_difficulty
Score up to 10 keywords in one call. Cost: 10 credits per keyword. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
batch_keyword_difficulty accepts 4 parameters: store, country, keywords, language. Required: keywords. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for batch_keyword_difficulty: 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.
batch_keyword_difficulty 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 batch_keyword_difficulty 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 batch_keyword_difficulty. 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.
batch_keyword_difficulty is provided by the MCP server (@getappniche/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue