Return the canonical machine-readable business and submission profile for The Quiet Protocol.
AI agents call get_submission_profile to retrieve information from Quiet Protocol Growth Offense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing profile data without creating, modifying, deleting, executing code, or moving money. The verb 'return' and the read-only nature of fetching a canonical profile align with the Read category. Severity is low because exposure of this data would not enable destructive actions and is typically informational in nature for a service business audit platform.
From the tool's definition Tool name 'get_submission_profile' and description 'Return the canonical machine-readable business and submission profile' indicate a retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access get_submission_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quiet Protocol Growth Offense, and nothing reaches the server without passing your rules. This is the rule we recommend for get_submission_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_submission_profile": {}
}
} get_submission_profile 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.
Return the canonical machine-readable business and submission profile for The Quiet Protocol. It is categorised as a Read tool in the Quiet Protocol Growth Offense MCP Server, which means it retrieves data without modifying state.
Register the Quiet Protocol Growth Offense MCP server in PolicyLayer and add a rule for get_submission_profile: 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 Quiet Protocol Growth Offense. Nothing to install.
get_submission_profile 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_submission_profile 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_submission_profile. 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_submission_profile is provided by the Quiet Protocol Growth Offense MCP server (joeroy2027/tqp-site). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quiet Protocol Growth Offense, 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.
19 Quiet Protocol Growth Offense tools catalogued and risk-classified — across an index of 43,000+ MCP servers.