Build a contributor-query response: given a signed SettlementRecord and a contributor DID, return per-axis (total_weight, contribution_count, merkle_path, axis_root) plus the full signed record so a third party can verify the contributor's share end-to-end without trusting the gateway beyond its ...
AI agents call aps_build_contributor_query to retrieve information from Agent Passport System — Cryptographic Identity for AI Agents without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
record | object | — | A signed SettlementRecord |
gateway_jwks | string | — | Advisory JWKS URL; not part of the signed material |
contributor_did | string | Yes | Contributor DID (data source, compute provider, governance signer, or protocol module identifier) |
Parameters from the server's own tool schema.
The tool reads from an existing signed SettlementRecord and returns structured verification data (merkle paths, weights, counts) for a given contributor DID. It does not modify, create, or delete data.
From the tool's definition 'Build a contributor-query response' and 'return per-axis (total_weight, contribution_count, merkle_path, axis_root) plus the full signed record so a third party can verify the contributor's share end-to-end' — this is a read/query operation that retrieves…
Documented attack patterns abuse exactly the kind of access aps_build_contributor_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for aps_build_contributor_query:
{
"version": "1",
"default": "deny",
"tools": {
"aps_build_contributor_query": {}
}
}aps_build_contributor_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 150 Agent Passport System — Cryptographic Identity for AI Agents tools →
Build a contributor-query response: given a signed SettlementRecord and a contributor DID, return per-axis (total_weight, contribution_count, merkle_path, axis_root) plus the full signed record so a third party can verify the contributor's share end-to-end without trusting the gateway beyond its public key. Returns null if the contributor has no share in the period. It is categorised as a Read tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it retrieves data without modifying state.
aps_build_contributor_query accepts 3 parameters: record, gateway_jwks, contributor_did. Required: contributor_did. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for aps_build_contributor_query: 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 Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.
aps_build_contributor_query 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 aps_build_contributor_query 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 aps_build_contributor_query. 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.
aps_build_contributor_query is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Passport System — Cryptographic Identity for AI Agents, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.