add_apu_item
AI agents use add_apu_item 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 tool creates or modifies data (adding APU items) within the budgeting system, which is reversible through update or deletion operations. This is a Write operation rather than Destructive. However, confidence is moderate (0.75) because the tool description is empty, limiting definitive classification.
From the tool's definition Tool name 'add_apu_item' and server description indicate this tool adds items to Unit Price Analysis (APU) within a budgeting system.
Attacks that exploit this kind of access
add_apu_item. 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 add_apu_item: 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.
add_apu_item 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 add_apu_item 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 add_apu_item. 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.
add_apu_item 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 →