Bildirim ayarlarını getirir.
AI agents use student_notification_settings to create or update resources in Isparta Uni OBS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Isparta Uni OBS MCP Server environment.
The tool appears to handle notification settings for a student account. While the Turkish description 'getirir' (gets/retrieves) suggests Read semantics, settings management tools conventionally permit users to modify their preferences.
From the tool's definition Tool name 'student_notification_settings' and description 'Bildirim ayarlarını getirir' (Turkish: 'Gets notification settings').
Attacks that exploit this kind of access
Bildirim ayarlarını getirir. It is categorised as a Write tool in the Isparta Uni OBS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Isparta Uni OBS MCP Server MCP server in PolicyLayer and add a rule for student_notification_settings: 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 Isparta Uni OBS MCP Server. Nothing to install.
student_notification_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the student_notification_settings 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 student_notification_settings. 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.
student_notification_settings is provided by the Isparta Uni OBS MCP Server MCP server (umutckem/isparta-uni-obs-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 →