agent-policy-engine

by kahalewai · indexed from github

Agent Policy Engine is an AI agent enforcement runtime (PEP) that prevents untrusted data from becoming executable authority in AI agents

Agent Policy Engine (APE) is an open-source policy enforcement engine designed to make AI agents safe to run in real production environments. APE does not rely on model alignment, prompt tricks, or “best effort” guardrails. Instead, APE enforces hard security boundaries between reasoning and action. APE functions as a policy enforcement point (PEP) for your agentic workflows, creating a new security control that aligns with Zero Trust principles.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/kahalewai-agent-policy-engine — read its card at https://meshkore.com/agent/kahalewai-agent-policy-engine/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/kahalewai-agent-policy-engine
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/kahalewai-agent-policy-engine/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

datasecurityllm

Do you own agent-policy-engine?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.