create_work_package
Crea un work package en OpenProject. Requiere OPENPROJECT_ALLOW_WRITE=true. Parámetros: project_id, subject, type_id (opcional), description (opcional), assignee_id (opcional), status_id (opcional), priority_id (opcional), start_date (opcional), due_date (opcional). Retorna: {id, subject, type, s...
This record as markdown: /tools/inggerman-mcps/create-work-package.md
What create_work_package does on MCP Framework Personal
AI agents use create_work_package to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.
Why create_work_package is rated Medium
An AI agent can call create_work_package faster than any human can review: one bad instruction and it creates or modifies resources in MCP Framework Personal by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_work_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_work_package, this is the rule to start with:
create_work_package 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 MCP Framework Personal, apply this rule, and every create_work_package call is checked against it from then on.
Questions about create_work_package
Crea un work package en OpenProject. Requiere OPENPROJECT_ALLOW_WRITE=true. Parámetros: project_id, subject, type_id (opcional), description (opcional), assignee_id (opcional), status_id (opcional), priority_id (opcional), start_date (opcional), due_date (opcional). Retorna: {id, subject, type, status}. It is categorised as a Write tool in the MCP Framework Personal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for create_work_package: 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 Framework Personal. Nothing to install.
create_work_package 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 create_work_package 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 create_work_package. 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.
create_work_package is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue