Get details for a specific pipeline in a workspace.
AI agents call get_pipeline_details to retrieve information from Mcp Openhexa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about a pipeline. It performs no modifications, deletions, financial transactions, or code execution. The action is purely informational querying of existing data within the OpenHEXA platform. Even if misused by an AI agent, the blast radius is minimal—at worst, an agent could discover information it shouldn't have access to, but no data would be altered or systems affected.
From the tool's definition Tool name 'get_pipeline_details' and description 'Get details for a specific pipeline in a workspace' indicate a read operation that retrieves information without modifying or executing anything.
Attacks that exploit this kind of access
Get details for a specific pipeline in a workspace. It is categorised as a Read tool in the Mcp Openhexa MCP Server, which means it retrieves data without modifying state.
Register the Mcp Openhexa MCP server in PolicyLayer and add a rule for get_pipeline_details: 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 Openhexa. Nothing to install.
get_pipeline_details 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_pipeline_details 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_pipeline_details. 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_pipeline_details is provided by the Mcp Openhexa MCP server (mcrimi/mcp-openhexa). 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 →