get_public_paths
List a DenkOps project's public (unauthenticated) paths, plus the routes DenkOps has observed the app serve.
This record as markdown: /tools/denkopsai-mcp/get-public-paths.md
What get_public_paths does on Denkopsai
AI agents call get_public_paths to retrieve information from Denkopsai 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 |
|---|---|---|---|
project_id | string | Yes |
Parameters from the server's own tool schema.
Why get_public_paths is rated Low
This tool performs a read-only operation that queries and retrieves information about public paths and routes in a DenkOps project. It has no capability to modify, create, delete, or execute operations. The low severity reflects minimal blast radius—an AI agent could only gather network/routing information, which could inform reconnaissance but cannot directly harm systems or data.
From the tool's definition Tool description explicitly states 'List' operation, describing retrieval of public paths and observed routes with no modification, deletion, or execution capability. No destructive or side-effect-producing actions are indicated.
Attacks that exploit this kind of access
The rule that runs get_public_paths safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_public_paths, this is the rule to start with:
get_public_paths 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 Denkopsai, apply this rule, and every get_public_paths call is checked against it from then on.
Questions about get_public_paths
List a DenkOps project's public (unauthenticated) paths, plus the routes DenkOps has observed the app serve. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
get_public_paths accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for get_public_paths: 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 Denkopsai. Nothing to install.
get_public_paths 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_public_paths 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_public_paths. 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_public_paths is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue