Read and return the full JSON content of a profile file.
AI agents call get_profile_content to retrieve information from OrcaSlicer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries profile configuration data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns existing profile information as JSON, which has no side effects on the system or the profiles themselves.
From the tool's definition Tool name is 'get_profile_content' and description states 'Read and return the full JSON content of a profile file.' The verb 'read' and 'return' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
Read and return the full JSON content of a profile file. It is categorised as a Read tool in the OrcaSlicer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OrcaSlicer MCP Server MCP server in PolicyLayer and add a rule for get_profile_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 OrcaSlicer MCP Server. Nothing to install.
get_profile_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_profile_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_profile_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_profile_content is provided by the OrcaSlicer MCP Server MCP server (itsumonotakumi/orcaslicer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →