get_chord_chart
Get the current chord chart information
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/get-chord-chart.md
What get_chord_chart does on Propresenter
AI agents call get_chord_chart to retrieve information from Propresenter without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_chord_chart is rated Low
This tool performs a query/retrieval action to fetch chord chart data from ProPresenter 7. It has no capability to modify, delete, or execute operations—it simply reads and returns existing information. The blast radius of misuse is minimal, as an agent cannot cause harm by reading chord charts.
From the tool's definition Tool name 'get_chord_chart' and description 'Get the current chord chart information' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_chord_chart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Propresenter, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_chord_chart, this is the rule to start with:
get_chord_chart 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 Propresenter, apply this rule, and every get_chord_chart call is checked against it from then on.
Questions about get_chord_chart
Get the current chord chart information. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.
Register the Propresenter MCP server in PolicyLayer and add a rule for get_chord_chart: 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 Propresenter. Nothing to install.
get_chord_chart 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_chord_chart 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_chord_chart. 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_chord_chart is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Propresenter, and thousands of servers like it.
This server
Across the catalogue