check_typosquat
Typosquat detector. USE WHEN: name differs from a well-known package by 1-2 chars (lodsh, reqeusts); copy-paste from unreliable source; downloads near zero but name looks familiar. RETURNS: {is_typosquat, likely_target, confidence}.
This record as markdown: /tools/dev-depscope-mcp/check-typosquat.md
What check_typosquat does on Depscope
AI agents call check_typosquat to retrieve information from Depscope 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 |
|---|---|---|---|
package | string | Yes | |
ecosystem | string | Yes |
Parameters from the server's own tool schema.
Why check_typosquat is rated Low
This tool queries package metadata to identify typosquatted packages and returns analysis results. It performs no write, execute, destructive, or financial operations. The capability is informational—detecting security risks rather than causing harm. The blast radius of misuse is minimal; false positives or negatives in typosquat detection would not cause direct damage. Classification as Read is appropriate.
From the tool's definition check_typosquat: Typosquat detector. RETURNS: {is_typosquat, likely_target, confidence}. No modifications, deletions, or side effects; purely analyzing and returning detection results.
Attacks that exploit this kind of access
The rule that runs check_typosquat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_typosquat, this is the rule to start with:
check_typosquat 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 Depscope, apply this rule, and every check_typosquat call is checked against it from then on.
Questions about check_typosquat
Typosquat detector. USE WHEN: name differs from a well-known package by 1-2 chars (lodsh, reqeusts); copy-paste from unreliable source; downloads near zero but name looks familiar. RETURNS: {is_typosquat, likely_target, confidence}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
check_typosquat accepts 2 parameters: package, ecosystem. Required: package, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for check_typosquat: 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 Depscope. Nothing to install.
check_typosquat 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 check_typosquat 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 check_typosquat. 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.
check_typosquat is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue