coding_engine_set
Choose which coding CLI this instance opens sessions with, and optionally the model it runs — e.g. switch to another engine, or off a model whose usage limit is spent.
This record as markdown: /tools/io-github-proagentstore-platform/coding-engine-set.md
What coding_engine_set does on ProAgentStore
AI agents use coding_engine_set to create or update resources in ProAgentStore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProAgentStore environment.
Why coding_engine_set is rated Medium
Modifies instance configuration by selecting coding engine and model settings, reversibly changeable.
From the tool's definition Choose which coding CLI this instance opens sessions with, optionally model
Attacks that exploit this kind of access
The rule that runs coding_engine_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coding_engine_set, this is the rule to start with:
coding_engine_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every coding_engine_set call is checked against it from then on.
Questions about coding_engine_set
Choose which coding CLI this instance opens sessions with, and optionally the model it runs — e.g. switch to another engine, or off a model whose usage limit is spent. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for coding_engine_set: 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 ProAgentStore. Nothing to install.
coding_engine_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the coding_engine_set 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 coding_engine_set. 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.
coding_engine_set is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue