check_openproject
Check OpenProject project management reachability via GET /api/v3/configuration. Returns 200 or 401 when service is up. Default port 80.
This record as markdown: /tools/aaronckj-mcp-nettools/check-openproject.md
What check_openproject does on Mcp Nettools
AI agents call check_openproject 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.
Why check_openproject is rated Low
This is a health check tool that queries a service endpoint using GET to verify its availability. It retrieves status information without side effects, making it a Read operation. The low severity reflects that it only gathers reachability information about an existing service without affecting system state or exposing sensitive data retrieval.
From the tool's definition Tool performs a GET request to /api/v3/configuration and returns status codes (200 or 401). The description explicitly states it 'checks reachability' and returns HTTP response codes, indicating passive health monitoring with no data modification, deletion,…
Attacks that exploit this kind of access
The rule that runs check_openproject 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_openproject, this is the rule to start with:
check_openproject 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 Nettools, apply this rule, and every check_openproject call is checked against it from then on.
Questions about check_openproject
Check OpenProject project management reachability via GET /api/v3/configuration. Returns 200 or 401 when service is up. Default port 80. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_openproject: 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.
check_openproject 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_openproject 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_openproject. 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_openproject 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.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue