get_workflow_section
AI agents call get_workflow_section to retrieve information from Engmanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve workflow information based on naming patterns and server context. No description provided, which slightly lowers confidence, but the sibling tools and server purpose (guidance/instructions) suggest read-only data retrieval with no side effects. Categorized as Read rather than Other because the context strongly implies a retrieval operation.
From the tool's definition Tool name 'get_workflow_section' with sibling tools 'get_next_step', 'get_project_info', 'list_available_projects', 'list_workflow_steps' all indicate retrieval operations.
Attacks that exploit this kind of access
get_workflow_section. It is categorised as a Read tool in the Engmanager MCP Server, which means it retrieves data without modifying state.
Register the Engmanager MCP server in PolicyLayer and add a rule for get_workflow_section: 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 Engmanager. Nothing to install.
get_workflow_section 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_workflow_section 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_workflow_section. 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_workflow_section is provided by the Engmanager MCP server (scarr7981/engmanager-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 →