Attach a durable artifact, proof URL, or preview to an existing OrgX entity. USE WHEN: saving evidence, PRs, documents, reports, screenshots, or external artifacts. For founder/team work, prefer practical artifact_type codes such as orchestration.next_initiative, eng.pull_request, eng.deploy_proo...
AI agents use orgx_attach to create or update resources in OrgX — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OrgX environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Target entity UUID or short ID prefix |
name | string | — | Artifact title |
type | string | — | Target entity type |
owner | string | — | Human or agent owner for the next review/action. Stored under metadata.artifact_contract. |
status | string | — | Artifact workflow status |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
metadata | object | — | Artifact metadata |
agent_type | string | — | Agent/domain that produced the artifact, such as engineering, sales, product, design, operations, marketing, or orchestrator. Stored under metadata.artifact_con |
session_id | string | — | Optional bootstrap/session identifier |
description | string | — | Artifact description |
review_date | string | — | Date or cadence for the next review point. Stored under metadata.artifact_contract. |
artifact_url | string | — | Internal artifact URL |
Parameters from the server's own tool schema.
An AI agent can call orgx_attach faster than any human can review — one bad instruction and it creates or modifies resources in OrgX by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (35 properties)
Documented attack patterns abuse exactly the kind of access orgx_attach gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for orgx_attach:
{
"version": "1",
"default": "deny",
"tools": {
"orgx_attach": {
"limits": [
{
"counter": "orgx_attach_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}orgx_attach 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.
Free to start. No card required.
Attach a durable artifact, proof URL, or preview to an existing OrgX entity. USE WHEN: saving evidence, PRs, documents, reports, screenshots, or external artifacts. For founder/team work, prefer practical artifact_type codes such as orchestration.next_initiative, eng.pull_request, eng.deploy_proof, eng.structured_blocker, sales.strategy, sales.icp_offer_sequence, sales.send_plan, marketing.launch_asset, marketing.channel_hypothesis, product.customer_discovery, product.prd, product.pricing_hypothesis, product.decision_record, design.audit, design.component_spec, design.token_package, ops.operator_brief, ops.runbook, ops.budget_envelope, ops.incident_status, proof.link. Include business_outcome, owner/review_date, and verification when the artifact should close agent work. NEXT: use orgx_submit_receipt to close attribution/quality loops or orgx_act to complete with proof. DO NOT USE WHEN: creating generic entities; use orgx_write. It is categorised as a Write tool in the OrgX MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
orgx_attach accepts 12 parameters: id, name, type, owner, status, _context, metadata, agent_type, session_id, description, review_date, artifact_url. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for orgx_attach: 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 OrgX. Nothing to install.
orgx_attach 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 orgx_attach 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 orgx_attach. 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.
orgx_attach is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.