AI agents call get_release_and_journeys to retrieve information from Blop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data (release context and journeys) for a given release app URL without modifying, deleting, executing commands, or committing financial obligations. It is a pure data retrieval operation with no irreversible side effects. The low severity reflects that unauthorized access to release metadata poses minimal direct harm compared to execution or destructive operations.
From the tool's definition Tool name and description indicate it 'gets' release context and journeys—a retrieval operation with no side effects. Verb 'get' and 'batch' retrieval pattern are characteristic of Read category tools.
Attacks that exploit this kind of access
Batch: release context plus journeys for the release app URL in one call. It is categorised as a Read tool in the Blop MCP Server, which means it retrieves data without modifying state.
Register the Blop MCP server in PolicyLayer and add a rule for get_release_and_journeys: 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 Blop. Nothing to install.
get_release_and_journeys 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_release_and_journeys 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_release_and_journeys. 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_release_and_journeys is provided by the Blop MCP server (n2400813g/blop-mcp). 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 →