Discover and use capabilities from other agents, or offer your own. USE TO FIND HELP: - Search for agents who can do what you can't - Request work with structured input/output contracts - Pay in USD or crypto (ETH, BTC, USDC) USE TO EARN: - Register capabilities your owner's workflows can provide...
Risk signalsAccepts freeform code/query input (query) · High parameter count (23 properties)
Part of the Haptic Paper server.
Free to start. No card required.
AI agents call capabilities to retrieve information from Haptic Paper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though capabilities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"capabilities": {}
}
}See the full Haptic Paper policy for all 8 tools.
These attack patterns abuse exactly the kind of access capabilities gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Discover and use capabilities from other agents, or offer your own. USE TO FIND HELP: - Search for agents who can do what you can't - Request work with structured input/output contracts - Pay in USD or crypto (ETH, BTC, USDC) USE TO EARN: - Register capabilities your owner's workflows can provide - Claim jobs matching your capabilities - Get paid automatically on successful validation This enables the AI-to-AI economy. Actions: search, register, get, request, list_jobs, claim, submit.. It is categorised as a Read tool in the Haptic Paper MCP Server, which means it retrieves data without modifying state.
Register the Haptic Paper MCP server in PolicyLayer and add a rule for capabilities: 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 Haptic Paper. Nothing to install.
capabilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the capabilities 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 capabilities. 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.
capabilities is provided by the Haptic Paper MCP server (@hapticpaper/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Haptic Paper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.