ai_dj_set
AI agents use ai_dj_set to create or update resources in AI Producer Hub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI Producer Hub environment.
An AI agent can call ai_dj_set faster than any human can review — one bad instruction and it creates or modifies resources in AI Producer Hub by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
ai_dj_set. It is categorised as a Write tool in the AI Producer Hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI Producer Hub MCP server in PolicyLayer and add a rule for ai_dj_set: 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 AI Producer Hub. Nothing to install.
ai_dj_set 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 ai_dj_set 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 ai_dj_set. 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.
ai_dj_set is provided by the AI Producer Hub MCP server (sandraschi/ai-producer-hub). 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 →