get_keyword_difficulty
Score one keyword for difficulty and opportunity, on the App Store or Google Play. Cost: 10 credits.
This record as markdown: /tools/com-getappniche-mcp/get-keyword-difficulty.md
What get_keyword_difficulty does on Mcp
AI agents call get_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'). |
keyword | string | Yes | Search term to score as an ASO target, e.g. 'habit tracker'. |
language | string | — | Language code the keyword is written in, e.g. 'en', 'de', 'pt-BR' (default 'en'). |
Parameters from the server's own tool schema.
Why get_keyword_difficulty is rated Low
This tool queries keyword metrics (difficulty and opportunity scores) and returns analytical data. It retrieves information without side effects, matching the Read category definition. The severity is low because misuse would only expose redundant ASO keyword data, not enable harmful actions or data loss. Confidence is high because the description clearly indicates a read-only scoring/analysis function.
From the tool's definition Tool description states it 'Score[s] one keyword for difficulty and opportunity' — purely a lookup/scoring operation with no modification, deletion, or execution of external commands. The server provides 'app discovery, ASO keywords, reviews' data retrieval.
Attacks that exploit this kind of access
The rule that runs get_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 get_keyword_difficulty, this is the rule to start with:
get_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 get_keyword_difficulty call is checked against it from then on.
Questions about get_keyword_difficulty
Score one keyword for difficulty and opportunity, on the App Store or Google Play. Cost: 10 credits. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_keyword_difficulty accepts 4 parameters: store, country, keyword, language. Required: keyword. 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 get_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.
get_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 get_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 get_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.
get_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