This record as markdown: /tools/io-github-nograai-nogra-mcp/chain-pm-then-agent.md
What chain_pm_then_agent does on Nogra
AI agents invoke chain_pm_then_agent to trigger actions in Nogra. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why chain_pm_then_agent is rated High
The name implies orchestrating or chaining multiple operations (PM then agent), which aligns with Execute category. Sibling tools such as 'agent_exec_packet' and 'codex_dispatch' are execution-oriented, suggesting this tool triggers or sequences external operations. However, the empty description lowers confidence significantly.
From the tool's definition Tool name 'chain_pm_then_agent' suggests chaining a project management step followed by agent execution, consistent with sibling tools like 'agent_exec_packet' and 'codex_dispatch' which imply execution of operations.
Attacks that exploit this kind of access
The rule that runs chain_pm_then_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nogra, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chain_pm_then_agent, this is the rule to start with:
chain_pm_then_agent stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nogra, apply this rule, and every chain_pm_then_agent call is checked against it from then on.
Questions about chain_pm_then_agent
chain_pm_then_agent is a execute tool on the Nogra MCP server. It is categorised as a Execute tool in the Nogra MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nogra MCP server in PolicyLayer and add a rule for chain_pm_then_agent: 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 Nogra. Nothing to install.
chain_pm_then_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chain_pm_then_agent 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 chain_pm_then_agent. 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.
chain_pm_then_agent is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nogra, and thousands of servers like it.
This server
Across the catalogue