Read the content of a specific measure and staff from the connected score.
AI agents call get_measure_content to retrieve information from Mcp Score without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on score data. It retrieves information about musical notation within a specified measure and staff from an already-connected notation application. There are no side effects, no data modifications, no code execution, and no irreversible actions. The blast radius of misuse is minimal—an agent could only access existing score data it should already have visibility of.
From the tool's definition Tool name is 'get_measure_content' and description states 'Read the content of a specific measure and staff from the connected score.' The word 'Read' explicitly indicates data retrieval with no modifications.
Documented attack patterns abuse exactly the kind of access get_measure_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Score, and nothing reaches the server without passing your rules. This is the rule we recommend for get_measure_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_measure_content": {}
}
}get_measure_content 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.
Read the content of a specific measure and staff from the connected score. It is categorised as a Read tool in the Mcp Score MCP Server, which means it retrieves data without modifying state.
Register the Mcp Score MCP server in PolicyLayer and add a rule for get_measure_content: 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 Mcp Score. Nothing to install.
get_measure_content 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_measure_content 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_measure_content. 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_measure_content is provided by the Mcp Score MCP server (tskovlund/mcp-score). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Score, 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.
18 Mcp Score tools catalogued and risk-classified — across an index of 43,000+ MCP servers.