create_resource
AI agents use create_resource to create or update resources in Proflores MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proflores MCP Server environment.
The 'create_' prefix and context within a budgeting system indicate this tool creates new resource records, making it a Write operation. Confidence is reduced from 0.85 to 0.72 because the tool description is empty, preventing verification of exact parameters and effects. It is Write rather than Execute because creating a resource record is a standard data creation operation, not code execution or complex triggering.
From the tool's definition Tool name 'create_resource' indicates creation of a new resource entry. Server context shows it manages a budgeting system for clients, projects, and resources through Supabase backend.
Attacks that exploit this kind of access
create_resource. It is categorised as a Write tool in the Proflores MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proflores MCP Server MCP server in PolicyLayer and add a rule for create_resource: 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 Proflores MCP Server. Nothing to install.
create_resource 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_resource 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_resource. 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_resource is provided by the Proflores MCP Server MCP server (jjesusaf/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →