Fetch Juno documentation from GitHub repo. Full docs: https://github.com/junobuild/docs/tree/main/docs. Topics use underscore naming matching folder hierarchy (e.g. build_authentication, reference_cli_functions_build).
AI agents call juno_docs to retrieve information from Junobuild without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation from a GitHub repository. Fetching/reading documentation is a read-only operation that does not modify, execute code, delete data, or create financial obligations.
From the tool's definition Tool description states 'Fetch Juno documentation from GitHub repo' - this is a retrieval operation with no side effects. The action is to fetch/retrieve static documentation content.
Attacks that exploit this kind of access
Fetch Juno documentation from GitHub repo. Full docs: https://github.com/junobuild/docs/tree/main/docs. Topics use underscore naming matching folder hierarchy (e.g. build_authentication, reference_cli_functions_build). It is categorised as a Read tool in the Junobuild MCP Server, which means it retrieves data without modifying state.
Register the Junobuild MCP server in PolicyLayer and add a rule for juno_docs: 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 Junobuild. Nothing to install.
juno_docs 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 juno_docs 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 juno_docs. 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.
juno_docs is provided by the Junobuild MCP server (junobuild-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →