This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/my-contracts.md
What my_contracts does on MIDAS Protocol
AI agents call my_contracts 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.
Why my_contracts is rated Low
This tool retrieves existing contract information without side effects. It does not execute contracts, create new ones, modify terms, or initiate payments. The 'view' action is purely informational. While the contracts themselves may relate to financial obligations, accessing them is a read operation.
From the tool's definition Tool name 'my_contracts' and description 'View all your contracts' indicate a read-only operation that retrieves contract data without modification or execution of financial transactions.
Attacks that exploit this kind of access
The rule that runs my_contracts 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_contracts, this is the rule to start with:
my_contracts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every my_contracts call is checked against it from then on.
Questions about my_contracts
View all your contracts. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for my_contracts: 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.
my_contracts 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 my_contracts 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 my_contracts. 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.
my_contracts 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.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue