digimon_by_level

List Digimon filtered by evolution level.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/digimon-by-level.md

WHAT IT DOES

What digimon_by_level does on UnClick

AI agents call digimon_by_level to retrieve information from UnClick 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
`level`	string	Yes	Level: Fresh, In Training, Rookie, Champion, Ultimate, or Mega

Parameters from the server's own tool schema.

RISK

Why digimon_by_level is rated Low

This tool retrieves data about Digimon creatures based on a filter criterion (evolution level). It performs no creation, modification, deletion, code execution, or financial operations. It is a straightforward read-only data lookup with minimal security risk.

From the tool's definition Tool name 'digimon_by_level' and description 'List Digimon filtered by evolution level' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs digimon_by_level safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For digimon_by_level, this is the rule to start with:

digimon_by_level Allowed

digimon_by_level is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "digimon_by_level": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every digimon_by_level call is checked against it from then on.

FAQ

Questions about digimon_by_level

What does the digimon_by_level tool do? +

List Digimon filtered by evolution level. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does digimon_by_level accept? +

digimon_by_level accepts 1 parameter: level. Required: level. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on digimon_by_level? +

Register the UnClick MCP server in PolicyLayer and add a rule for digimon_by_level: 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 UnClick. Nothing to install.

What risk level is digimon_by_level? +

digimon_by_level is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit digimon_by_level? +

Yes. Add a rate_limit block to the digimon_by_level 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.

How do I block digimon_by_level completely? +

Set action: deny in the PolicyLayer policy for digimon_by_level. 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.

What MCP server provides digimon_by_level? +

digimon_by_level is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →