AI agents call juno_changes_list 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 and queries historical change data with optional filtering (--all, --every flags). It has no side effects, does not modify, delete, or execute operations. It is a pure information retrieval operation analogous to viewing a log or history, making it a Read category tool with low severity.
From the tool's definition Tool name contains 'list' and description explicitly states 'List all submitted or applied changes' with no modification capabilities mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all submitted or applied changes to your module. By default shows only submitted (pending) changes. Use --all for full history and --every to include all statuses. 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_changes_list: 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_changes_list 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_changes_list 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_changes_list. 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_changes_list 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 →