Your agent works in your customers' systems. Keep it inside your rules.
Flag or stop a dangerous call before it runs, and keep a record you can show their security team. Free, on your machine.
A bulk read of the internal user table, blocked before any data leaves.
In ten seconds: a DROP TABLE flagged, then stopped, and a sample of the file for that security team. No key, and your data does not leave your machine.
Then add @agentx_protect(agent_id="my_agent") to one real tool in your project. The next agentx evidence there lists the calls it flags and the sites named in its calls.
One decorator, @agentx_protect(agent_id="my_agent"), on any tool checks every call inside your own process before it runs, no key.
pip install agentx-security-sdk
agentx demoThe second line runs a ten-second offline demo: a DROP TABLE is flagged, then stopped, and the agent is told the safe way to do it.
import requests
from agentx_sdk import agentx_protect
@agentx_protect(agent_id="crm")
def call_api(url):
return requests.get(url)
# the agent picks the url at runtime:
call_api("http://169.254.169.254/")The tool behaves exactly as it does today: the wrap watches and records, and blocks nothing. Add posture="enforce" to the decorator above when you want it stopping calls, and it keeps blocking until you delete the argument. See what it recorded with agentx audit
Step up to the gateway below for more rules and Recover.
One line in mcp.json wraps any local server. It catches the dangerous tools/call; turn on blocking and it never reaches the server, and the agent is coached to self-correct, no key.
{
"mcpServers": {
"filesystem": {
"command": "uvx",
"args": [
"agentx-mcp", "npx", "-y",
"@modelcontextprotocol/server-filesystem",
"/data"
]
}
}
}Config uses uvx (no install). Want to watch it block something first?
Trying it on servers you already use? A wrapped server records every call and blocks none of them. AGENTX_POSTURE=enforce in that server's env is how you make it start blocking. Add it per server block; the ones you leave alone keep watching. Read it back with uvx agentx-mcp --audit.
This is keyless and it is your protection for MCP servers today. Gateway-backed Recover over MCP is on the roadmap.
Want the gateway to cover your MCP traffic too?
Wrap a tool in one line. Every call it makes is written down on your machine (tool and argument names, no values), and audit prints what your agent did. Nothing is blocked, so your agent runs as it does today.
npm install @agentx-core/security-sdkimport { agentxWatchAll }
from "@agentx-core/security-sdk";
// was: tools: { runSql, sendEmail }
tools: agentxWatchAll({ runSql, sendEmail })Your tools behave exactly as they do today: the wrap watches and records, and blocks nothing. See what it recorded with npx @agentx-core/security-sdk audit
Inventory first? Lists every tool your agent can call, ranked by risk, with no install:
npx @agentx-core/scan .To block TypeScript tools, wrap them with agentxProtect and set AGENTX_API_KEY (and AGENTX_GATEWAY_URL for a gateway that is not on this machine): the gateway checks each call before it runs. If it cannot answer, the call runs unchecked unless AGENTX_FAIL_MODE=closed.
What you add when you want more. Extra rules and the checks a keyword match can't do, coached recovery that finishes the run, and team review before a risky action runs.
The Python decorator and the agentx-mcp proxy run the keyless check first, and the TypeScript SDK watches and records, all with no key and nothing but counts leaving your machine. The gateway adds more rules and Recover: use ours with a free key and nothing to run, with your team's rules set in one place on the website, or run your own with your own Gemini key. Over MCP it is on the roadmap.
Full quickstart for your language → one numbered path, start to finish.
One decorator on a Python tool, one line in your mcp.json, or one line around a TypeScript tool. Python and MCP check every call against the keyless rules (DROP TABLE, secret exfiltration, SSRF), Python also against a site allowlist per agent, and write down what they find; TypeScript writes down every call. Nothing is blocked until you set AGENTX_POSTURE=enforce (Python and MCP). agentx evidence writes the file for your customer's security team. No LLM key, no signup.
record + report
The gateway adds more rules and the checks a keyword match can't do, and tracks session state: budget ceilings and no-progress loop breaking that a single stateless call can't see. Its judge catches what keyword rules can't, writes the safe path when your policy carries none, and runs the coach-and-retry for you, so your agent finishes the task instead of dying on a 403. Use our hosted gateway with a free key, or run your own with your own Gemini key. An install with an AGENTX_API_KEY set enforces by default: what Watch wrote down, Recover stops. Set AGENTX_POSTURE=audit any time you want it watching instead.
guide + continue
Get the gatewayYour team's rules, set once. Write a rule, and Claude Code asks first on every teammate's machine. Change it on the website and every machine follows within minutes. Approve or deny your agents' calls from the page, and hand a customer's security team one file listing every rule.
review + govern
Start freeWhat AgentX catches today
The calls you can't take back, grouped. In Python and MCP, the first four groups are caught before the call runs, with no model call and no API key. Out of the box AgentX records them; turn on blocking and the same checks stop them. The last two need the gateway. Drawn from a public catalog we maintain of real agent failures.
Destructive data ops
DROP TABLETRUNCATEDELETE without WHEREALTER DROP COLUMNFlagged, or blocked with enforce on
Secret & PII exfiltration
credential / secret readsnamed-PII customer readspastebin, gist, transfer.sh, webhook.siteFlagged, or blocked with enforce on
SSRF & network traversal
169.254.169.254loopback / link-localmass port scan (nmap)Flagged, or blocked with enforce on
Shell & files
rm -rf / or ~disk wipe (dd, mkfs)path traversal → /etc/shadowcurl | shFlagged, or blocked with enforce on
Cloud teardown (terraform destroy, whole bucket and volume deletes) is checked by the gateway, not yet by the free local check.
Money, comms & dependencies
payment over the limitrunaway spend (budget ceiling)runaway provisioning (fleet ceiling)inbox / bulk wipeexternal publishunverified installThe gateway can hold these for human approval
Runaway loops
no-progress command loopstuck-command repeatThe gateway stops these after they repeat