AI agents invoke submit_task to trigger actions in Openaaas Mcp Adapter. 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.
This tool submits tasks to a remote agent for execution. The effects depend entirely on the arguments (task type, parameters, uploaded files), making it an Execute-category tool. The blast radius is high because arbitrary tasks can be dispatched to a scientific agent network, potentially triggering compute-intensive or consequential operations on remote systems.
From the tool's definition 提交任务到远程 Agent（支持文件上传）— 'submit task to remote Agent (supports file upload)'
Documented attack patterns abuse exactly the kind of access submit_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openaaas Mcp Adapter, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_task:
{
"version": "1",
"default": "deny",
"tools": {
"submit_task": {
"limits": [
{
"counter": "submit_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}submit_task 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.
Free to start. No card required.
提交任务到远程 Agent（支持文件上传）. It is categorised as a Execute tool in the Openaaas Mcp Adapter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openaaas Mcp Adapter MCP server in PolicyLayer and add a rule for submit_task: 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 Openaaas Mcp Adapter. Nothing to install.
submit_task 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 submit_task 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 submit_task. 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.
submit_task is provided by the Openaaas Mcp Adapter MCP server (wolido/openaaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openaaas Mcp Adapter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Openaaas Mcp Adapter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.