create_custom_field

Define a user custom field for tasks.

Server Todos @hasna/todos
Category Write
Risk class Medium
Parameters 00 required

What create_custom_field does on Todos

AI agents use create_custom_field to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.

Why create_custom_field needs a policy

This tool creates or modifies task metadata by defining custom fields—a reversible operation that changes system configuration but does not execute code, delete data, or cause financial impact. It is a Write category tool with low severity since custom field creation has limited blast radius and can be undone.

From the tool's definition Tool name 'create_custom_field' and description 'Define a user custom field for tasks' indicate creating a new configuration/metadata field for task management system

Questions about create_custom_field

What does the create_custom_field tool do? +

Define a user custom field for tasks. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_custom_field? +

Register the Todos MCP server in PolicyLayer and add a rule for create_custom_field: 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 Todos. Nothing to install.

What risk level is create_custom_field? +

create_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_custom_field? +

Yes. Add a rate_limit block to the create_custom_field 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.

How do I block create_custom_field completely? +

Set action: deny in the PolicyLayer policy for create_custom_field. 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.

What MCP server provides create_custom_field? +

create_custom_field is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.