Look up whether a specific wallet has an active verified-hireable subscription on the TensorFeed Agent Directory. Returns { verified_hireable: bool, verified_hireable_until?: ISO } for a given wallet. Useful for downstream marketplaces or peer agents who want to confirm a published-rate or active...
AI agents call get_verified_hireable_status to retrieve information from TensorFeed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet | string | Yes | EIP-55 or lowercased wallet address (0x + 40 hex). |
Parameters from the server's own tool schema.
This tool retrieves subscription status metadata from a directory for verification purposes. It has no side effects—it queries existing data (verified_hireable status and expiration timestamp) without creating, modifying, deleting, or executing anything. The use case ('confirm a published-rate or active-availability badge is current before routing work') is purely informational lookup.
From the tool's definition Tool description states it 'Look[s] up' and 'Returns' subscription status information. The verb 'look up' and the return of a boolean flag with optional timestamp indicate a read-only query operation with no data modification, deletion, or state change…
Attacks that exploit this kind of access
Look up whether a specific wallet has an active verified-hireable subscription on the TensorFeed Agent Directory. Returns { verified_hireable: bool, verified_hireable_until?: ISO } for a given wallet. Useful for downstream marketplaces or peer agents who want to confirm a published-rate or active-availability badge is current before routing work to that wallet. It is categorised as a Read tool in the TensorFeed MCP Server, which means it retrieves data without modifying state.
get_verified_hireable_status accepts 1 parameter: wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.
Register the TensorFeed MCP server in PolicyLayer and add a rule for get_verified_hireable_status: 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 TensorFeed. Nothing to install.
get_verified_hireable_status 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 get_verified_hireable_status 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 get_verified_hireable_status. 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.
get_verified_hireable_status is provided by the TensorFeed MCP server (https://mcp.tensorfeed.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →