Deploy Agent Tool Policy
Check proposed tool names against an explicit allowlist
Tool
Just deployed
Deploy and Host Agent Tool Policy on Railway
Check proposed tool names against an explicit allowlist.
About Hosting Agent Tool Policy
This is a stateless JSON tool. Deploy it, copy TOOL_TOKEN from service variables and send it as an Authorization: Bearer header on POST /run. The /health endpoint is public and returns readiness only. Inputs are limited to 64 KiB. The application does not store requests or call a model.
Why Deploy Agent Tool Policy
Call a deterministic operation from an agent, workflow or application without an LLM API key.
Common Use Cases
- Check proposed tool names against an explicit allowlist.
- Insert a deterministic check or transformation in a workflow.
- Repeat the documented example in a regression check.
Dependencies for Agent Tool Policy
- Python 3.13 container and a Railway project.
- An HTTP client with your generated bearer token.
Example input for POST /run
{"calls": ["read", "write"], "allowed": ["read"]}
Expected response
{"result": ["write"]}
The single process is intended for small internal workloads. Set concurrency and load limits upstream before serving high volume traffic.
Template Content
Tool
python:3.13-slim
