my_negotiations

View all your negotiations

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp

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/io-github-bbrainfrance-midas-protocol/my-negotiations.md

WHAT IT DOES

What my_negotiations does on MIDAS Protocol

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

RISK

Why my_negotiations is rated Low

This tool queries and retrieves existing negotiation data without creating side effects, modifying records, executing operations, or committing financial transactions. It is a straightforward data retrieval function, placing it in the Read category with low severity due to minimal blast radius—an agent misusing it can only access the user's own negotiation history.

From the tool's definition Tool name 'my_negotiations' and description 'View all your negotiations' indicate a retrieval operation with no modification capability. The verb 'view' and lack of any action words (create, delete, execute, pay) confirm read-only semantics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs my_negotiations safely

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

my_negotiations Allowed

my_negotiations 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": {
    "my_negotiations": {}
  }
}

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

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

FAQ

Questions about my_negotiations

What does the my_negotiations tool do? +

View all your negotiations. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on my_negotiations? +

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

What risk level is my_negotiations? +

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

Can I rate-limit my_negotiations? +

Yes. Add a rate_limit block to the my_negotiations 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 my_negotiations completely? +

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

my_negotiations is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MIDAS Protocol, and thousands of servers like it.

This server

All 44 MIDAS Protocol tools →

Across the catalogue

The MCP Attack Database →

Guides

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