get_co_sign_pairs

List agent↔MCP founding co-sign pairs and completion status (real feedback only).

SERVERDual Registry SOURCEhttps://www.dualregistry.dev/api/protocol

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-dualregistry-registry/get-co-sign-pairs.md

WHAT IT DOES

What get_co_sign_pairs does on Dual Registry

AI agents call get_co_sign_pairs to retrieve information from Dual Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_co_sign_pairs is rated Low

Even though get_co_sign_pairs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_co_sign_pairs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_co_sign_pairs, this is the rule to start with:

get_co_sign_pairs Allowed

get_co_sign_pairs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_co_sign_pairs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every get_co_sign_pairs call is checked against it from then on.

FAQ

Questions about get_co_sign_pairs

What does the get_co_sign_pairs tool do? +

List agent↔MCP founding co-sign pairs and completion status (real feedback only). It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_co_sign_pairs? +

Register the Dual Registry MCP server in PolicyLayer and add a rule for get_co_sign_pairs: 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 Dual Registry. Nothing to install.

What risk level is get_co_sign_pairs? +

get_co_sign_pairs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_co_sign_pairs? +

Yes. Add a rate_limit block to the get_co_sign_pairs 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.

How do I block get_co_sign_pairs completely? +

Set action: deny in the PolicyLayer policy for get_co_sign_pairs. 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.

What MCP server provides get_co_sign_pairs? +

get_co_sign_pairs is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dual Registry, and thousands of servers like it.

This server

All 64 Dual Registry tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →