check_vikunja

Check Vikunja task manager health via GET /api/v1/info. Returns version and build information.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-vikunja.md

WHAT IT DOES

What check_vikunja does on Mcp Nettools

AI agents call check_vikunja to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_vikunja is rated Low

This tool retrieves diagnostic information about a Vikunja task manager instance's health status and metadata. It uses a GET HTTP method which is inherently read-only, returns informational data only (version, build info), and cannot modify, delete, or execute code. The blast radius of misuse is minimal—exposing version information could aid reconnaissance but causes no direct harm.

From the tool's definition Tool description states it performs a GET request to retrieve version and build information from a Vikunja API endpoint. GET requests are read-only operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_vikunja safely

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

check_vikunja Allowed

check_vikunja 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": {
    "check_vikunja": {}
  }
}

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

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

FAQ

Questions about check_vikunja

What does the check_vikunja tool do? +

Check Vikunja task manager health via GET /api/v1/info. Returns version and build information. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_vikunja? +

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

What risk level is check_vikunja? +

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

Can I rate-limit check_vikunja? +

Yes. Add a rate_limit block to the check_vikunja 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 check_vikunja completely? +

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

check_vikunja is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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